This guide was adapted from https://gist.github.com/niw/e4313b9c14e968764a52375da41b4278#running-ubuntu-server-for-arm64
- Install Xcode from App Store or install Command Line Tools on your Mac running on Apple Silicon.
This guide was adapted from https://gist.github.com/niw/e4313b9c14e968764a52375da41b4278#running-ubuntu-server-for-arm64
Let me start off by saying what is nice about Python:
import
system makes it easy to trace the filepath for any dependency.### | |
### script to detect objects in live video | |
### using MobileNets+SDD | |
### | |
### by: memeka <[email protected]> | |
### | |
import argparse, json | |
import time, datetime, threading | |
import numpy, cv2 |
This configuration worked for me, hope it helps
It is based on: https://becominghuman.ai/deep-learning-gaming-build-with-nvidia-titan-xp-and-macbook-pro-with-thunderbolt2-5ceee7167f8b
and on: https://stackoverflow.com/questions/44744737/tensorflow-mac-os-gpu-support
# # IE 10 + | |
# # Firefox 27 + | |
# # Safari 7 + | |
# # iOS Safari 5 + | |
# # IE mobile 10 + | |
# # Android 4.2 + | |
# # Blackberry 10 + | |
# # Chrome 31+ | |
# |
Quite a lot of different people have been on the same trail of thought. Gary Bernhardt's formulation of a "functional core, imperative shell" seems to be the most voiced.
"Imperative shell" that wraps and uses your "functional core".. The result of this is that the shell has fewer paths, but more dependencies. The core contains no dependencies, but encapsulates the different logic paths. So we’re encapsulating dependencies on one side, and business logic on the other side. Or put another way, the way to figure out the separation is by doing as much as you can without mutation, and then encapsulating the mutation separately. Functional core — Many fast unit tests. Imperative shell — Few integration tests