How to train your own object detection models using the TensorFlow Object Detection API (2020 Update)
This started as a summary of this nice tutorial, but has since then become its own thing.
This started as a summary of this nice tutorial, but has since then become its own thing.
Reposted from Qiita
For almost a year now, I've been using this "flux" architecture to organize my React applications and to work on other people's projects, and its popularity has grown quite a lot, to the point where it shows up on job listings for React and a lot of people get confused about what it is.
There are a billion explainations on the internet, so I'll skip explaining the parts. Instead, let's cut to the chase -- the main parts I hate about flux are the Dispatcher and the Store's own updating mechanism.
If you use a setup similar to the examples in facebook/flux, and you use flux.Dispatcher, you probably have this kind of flow:
Add Enable=Source
to /etc/bluetooth/audio.conf right after [General]
.
Find address in form XX:XX:XX:XX:XX:XX of phone with hcitool scan
.
Pair and trust smartphone with sudo bluez-simple-agent hci0 XX:XX:XX:XX:XX:XX
and sudo bluez-test-device trusted XX:XX:XX:XX:XX:XX yes
.
Create loopback in pulseaudio connection bluetooth a2dp source with alsa sink:
Create an unprivileged Linux container (LXC) dedicated to running Wordpress websites.
If you install Wordpress regularly on Linux you can instead simply clone this container.
The Wordpress installation is nothing fancy. It's not multi-site, it's not SSL enabled by default, or anything like that. Just a plain bog-standard Wordpress installation serving a single domain.
var util = require('util'), | |
EventEmitter = require('events').EventEmitter; | |
var Server = function() { | |
var self = this; | |
this.on('custom_event', function() { | |
self.logSomething('custom_event'); | |
}); |
After having the same issue myself by using a mainline 5.13 kernel in Pop OS, I managed to get the monitors working by having a look at the guide for porting the driver to other distros here: https://support.displaylink.com/knowledgebase/articles/679060-porting-the-displaylink-ubuntu-driver-to-other-lin
A small summary though (only tested in PopOs, but should probably work in most Debian/Ubuntu based distros):
sudo ./displaylink-driver-5.4.0-55.153.run uninstall
./displaylink-driver-5.4.1-55.174.run --noexec --keep
<?php | |
/** | |
* This program is free software. It comes without any warranty, to | |
* the extent permitted by applicable law. You can redistribute it | |
* and/or modify it under the terms of the Do What The Fuck You Want | |
* To Public License, Version 2, as published by Sam Hocevar. See | |
* http://sam.zoy.org/wtfpl/COPYING for more details. | |
*/ | |
/** |
<annotation> | |
<folder>GeneratedData_Train</folder> | |
<filename>000001.png</filename> | |
<path>/my/path/GeneratedData_Train/000001.png</path> | |
<source> | |
<database>Unknown</database> | |
</source> | |
<size> | |
<width>224</width> | |
<height>224</height> |
This guide has been updated for Titanium SDK 3.3.0 which uses AppCompat to bring the ActionBar to Android 2.3.x
Android has a build-in theming system. Using this feature you can easily change the base color Android uses for its controls across your app, allowing you to provide better branding and personalization, while maintaining Android's UI and UX.
Android built-in themes are: