I'm trying to create a GOTURN tracker using opencv, but the process finishes with error:
self.tracker = cv2.Tracker_create("GOTURN")
Process finished with exit code 139
If I change the type of tracker to MIL, BOOSTING, MEDIANFLOW, TLD or KCF it works well.
It seems the python api doesn't support this kind of tracker yet, is that so?
I was looking at the master branch of 3.2 version, so Goturn is not included in 3.1 version. Have to wait.
http://docs.opencv.org/3.2.0/df/ddd/tracker_8hpp.html
Related
I'm seeing signs that my CockroachDB cluster isn't able to finalize a version upgrade: SHOW CLUSTER SETTING version shows a version older than the binary's version, and I'm getting errors when trying to use new features or run commands that reference system tables. How can I find out why it's not upgrading?
If you run
SET CLUSTER SETTING version = crdb_internal.node_executable_version();
You should get an informative error message explaining why it can't do that. Stuck upgrades almost always indicate a bug and should be reported to Cockroach Labs (via a Github issue or other support channels).
I'm newbie in Opendaylight. I'm trying the very first example of ODL controller application by following this tutorial:
Controller Core Functionality Tutorials
Of course it was not updated so I had to modify something for the newest version (Carbon SR3, on Ubuntu 16.04 LTS). However, when I executed the program, I couldn't find the message
HelloProvider Session Initiated
by typing
log:display | grep Hello
It means my application was not started. On the other hand, I verified features but there was only odl-hello-api by default (no restconf, dlux, etc.). I had to modified karaf/pom.xml (karaf4-parent version 3.0.2-SNAPSHOT, adding dependencies for dlux-core and dluxapps) to install these features but of course I coudln't find my application in ODL graphic application.
Anyone has the same issues? Thanks in advance.
The core tutorials project is no longer maintained. I would suggest looking at the toaster sample documented at https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Toaster_Step-By-Step. To try your own project, use the startup archetype documented at https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-SAL:Startup_Project_Archetype.
I wanted to try STXXL to find how efficient it is in reading a big data file from the disk.
So i setup the enviornment for using it.
Then i ran this program http://algo2.iti.kit.edu/dementiev/stxxl/tags/1.2.1/algo_2sort__file_8cpp-example.html in VS2010. However the file data was not mapped to the vector_type, in fact it deleted the contents of the file after this statement - vector_type v(&f);
I tried changing from stxxl::file::RDWR to stxxl::file::RDONLY, this time the file content was not deleted, however still the vector_type variable was empty.Request your support to proceed further.
Also, is STXXL used widely in commercial applications?
Best Regards,
Ramki.
You are running a code example from STXXL version 1.2.1, which version have you installed on your system?
Most up-to-date version is "Development 1.4" which comes with many improvements, a comprehensive documentation with a lot of short code examples and runs pretty well - check the official STXXL Website under "Downloads and Documentation". Using version 1.4 is highly recommended.
Please check if your problem still exists on the new "Development 1.4" version. The Installation Process has become much easier - read the Installation and Configuration Part of the Documentation at first.
The official webpage provides a (certainly incomplete) list of Publications,Ongoing and Completed Projects using the STXXL successfully - there is no reason why not using it in an commercial environment.
im getting this error when im trying to update Meteor on windows.
Using git bash here, but getting the same error in command prompt.
Does the file simply not excist, or what is going on here, have had it for some days now, so im just curious if the file excist at all, since its not really officially supported on windows yet?
$ meteor update
New version available: 0.3.8
Failed to download: https://d3sqy0vbqsdhku.cloudfront.net/meteor-package-Windows
_NT-i686-0.3.8.tar.gz
It is not supported officially yet on Windows. You need to rely on weekly checking win.meteor.com for updates.
I believe you are correct in your assumption of it not really being officially supported on windows. I also get this same error and have tried everything to get around it. I tried scouring for this package manually and was unable to find it.
I have a mapreduce job whose role is to split my input file into two files according to a given criterion.
I am currently using Hadoop r0.20.203 because it is the current stable version
This version offers two APIs :
The old/deprecated one (org.apache.hadoop.mapred)
The new one (org.apache.hadoop.mapreduce)
As you can imagine, I am using the new API, and my problem is that Hadoop r0.20.203 does not offer any MultipleOutput formats in the new API.
Hadoop 0.20.203 stills offers MultipleTextOutputFormat and MultipleTextOutputs (which are both suitable for my case) in the old API. Moreover, the newer Hadoop 0.22 offers MultipleOutputs in the new API.
I see four solutions to my problem :
Switch to Hadoop 0.22. The problem with this solution is that the version may not be deployed on the clusters I'm using because of its beta status.
Use the old API for this specific job and the new one for the others. I have seen that the old API has been undeprecated in Hadoop 1.0.0, so can it still be used ? If I need to switch to a newer Hadoop version later, I would have only this job to rewrite.
Use the old API for all my jobs to avoid compatibility/consistency problems. Do you think it could harm the evolution of my program ? Especially if I need to switch to a newer Hadoop version later.
Forget about multiple outputs and find another solution.
What would you do if you were me ?
Because so much code relies on it, and because the new API (as you have discovered) was never fully implemented, they are probably un-deprecating the old API in a future version of Hadoop. I'd use the old API and not worry about it.
See http://www.cloudera.com/blog/2010/08/what%E2%80%99s-new-in-apache-hadoop-0-21/
Why don't you put the source code in your project and use it?
http://grepcode.com/file_/repository.cloudera.com/content/repositories/releases/com.cloudera.hadoop/hadoop-core/0.20.2-737/org/apache/hadoop/mapreduce/lib/output/MultipleOutputs.java/?v=source
It should be compatible with r0.20.203, actually I don't see classes which should not be available in the older version.
And there is really nothing magic about it, it just setup's several record writers for each configured output (type and stuff). I bet that you could have written your own in the time of formulating the question