trying to run openpose on windows.
tensorflow = 1.14 installed already.
getting the error no module found : tensorflow.contrib
is there any way to work out on this on windows?
or any other library to work for pose detection?
Please suggest a alternate way to do pose estimation if there is no solution to this problem for windows.
Thanks.
You got above error because tensorflow.contrib has been removed from the packages.
Since all the projects in tf.contrib were not officially supported by Tensorflow and it had designated owners for maintaining it.
From Tensorflow 2.x version all the contrib projects has three options: move to core, move to a separate repository or delete most of of them have been reviewed with the respective project owners.
If the library you are using is moved to the core or separate repository, then tensorflow automatic code migration from 1.x to 2.x will not work for tf.contrib` projects. You have to change code manually for above parts, which is suggested going forward.
You can refer this article for Pose Estimation using TensorFlow 2.0.
Related
I am trying to locate the last version of Caffe that was still compatible with cuDNN v2. The current master requires cuDNN v3. I've been searching through the github repository for Caffe trying to locate what I need but there doesn't seem to be a clear way of doing this. Is there a relatively painless way of finding this on github ?
Here is a list of Caffe release, and rc2 is the one you are looking for.
I just upgraded to version 3.0.1 from nunit 2.6.4. It used to have a NUnit Gui Runner, located here:
After installing 3.0.1 (which I downloaded windows version from here)
I now no longer see the nunit.exe in the installation folder, for example the directory structure is different and appears to be missing many files that were part of the previous installation:
The NUnit team decided to make the GUI a separate product and will be releasing it separately. It is being rewritten from the ground up for NUnit 3, but hasn't been released yet. Development is happening on the GitHub page at https://github.com/nunit/nunit-gui if you want to get involved or track the progress. Initial releases will be out soon.
Update - There have been several preview releases of the new NUnit GUI that can be found at https://github.com/nunit/nunit-gui/releases. The previews are not recommended for production use, but they work and can be used.
The "final" release is here, you can find it at: https://github.com/TestCentric/testcentric-gui/releases
For anyone coming to this page, looking where to find the NUnit Gui, please note that on http://nunit.org/?p=download you can get version 2.6.4, which does contain the Gui.
UPDATE
As pointed out in the comments, a lot has changed since, and you should no longer use the 2.x version tools, rather use the new TestCentric UI found at https://github.com/TestCentric/testcentric-gui/releases
We use the Entity Framework 6.1.2 NuGet package in 6 solutions. EF was just updated to 6.1.3 and we want to update all of the solutions to use the newest version. Taking the naive route we would open a solution in Visual Studio, use the NuGet Package Manager to update the package, close the solution, repeat for next solution. Running Update-Package EntityFramework in the Package Manager Console is probably a little more efficient than using the GUI but still requires opening each solution individually.
I'd love to be able to run a script which finds all the solutions in a folder and updates the package for (all projects in) each solution. I realize that updating the version number in the packages.config is not the same as installing the new version of a package, so that (very simple) option won't work. I also realize that there's not much efficiency to be gained by doing this one time, but libraries are updated so frequently these days keeping up to date can become an (admittedly minor) annoyance. Is it possible to automate this task?
I'm using the academic version of enthought python for Windows. Most of ogr works, but not geometry methods like geometry.Buffer() or predicates like geometry1.crosses(geometry2). According to this:
http://gdal.org/python/osgeo.ogr.Geometry-class.html#Crosses
ogr needs to have been built with GEOS. Has anybody got these methods to work with Enthought? If not, can you suggest a Windows python binary where these are working?
thanks,
jim
Correct, there are many possible build configurations of GDAL/OGR, and geos is not currently supported by Enthought's build configuration. We will consider adding it in a future build. Meanwhile, FYI, GEOS operations are fully supported in the powerful and popular Shapely package which is included in the Enthought repository.
I am using Autofac in a project that is being obfuscated using Dotfuscator. the dotfuscator fails saying it cannot find mscorlib version 2.0.5.0
Is there a way to tell Dotfuscator how to obfuscate Autofac with portable Dll?
Is Autofac team planning releasing autofac with reference to .NET 4.0?
Any other suggestions?
I don't know what version of Dotfuscator you're using, but it does seem that at least as of 4.9.9000 they "know" about Portable Class Libraries. If you aren't at that version and can't upgrade, you might need to contact Dotfuscator support to find out a solution. (Another question of similar nature also pointed to updating Dotfuscator as the answer.)
A similar sort of issue occurs with FxCop analysis and SecAnnotate. To get around those issues with those tools, you need to tell them to ignore version information on certain assemblies (like System.Core and mscorlib). You may need to use an option like that on Dotfuscator if such a thing exists.
PCL can also cause challenges on machines that don't have all the latest .NET patches. Make sure you're patched up.
There is no plan to release an Autofac tailored just to .NET 4.x Autofac is a Portable Class Library so it can support multiple platforms without conditional compilation, making for easier testing and development. It switched away from platform-specific builds as of 3.0 and there's no plan to go back.
If upgrading Dotfuscator and patching your machine doesn't fix the issue, your best bet is to find the Dotfuscator mechanism for ignoring assembly version.