ROS PTAM: cannot locate rosdep definition - ros

I am trying to install the latest PTAM (Parallel Tracking and Mapping) as described on the Installation page (http://wiki.ros.org/ethzasl_ptam#Installation). However, when running "rosdep install ptam" it yields the following error:
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
ptam: Cannot locate rosdep definition for [ptam_com]
I have followed the exact same procedure on a different system one month ago (before PTAM was changed to catkin) and it worked. The reason for changing the system is that the GUI of PTAM is said to be successfully loaded but it is actually not showing. So we changed to a new system with an nvidia graphics card.
I tried to retrieve the old version from Github on the new system but it yields the same error.
Many thanks.

ROS has its own very active answer forum. So questions like this should better be answered there. Besides,
Cannot locate rosdep definition for
This indicates that "ptam" is not yet registered as the rosdep key (I'm looking at Ubuntu).
The process for adding new keys may not be documented, but you could refer to thread like this and see if you can pick up.

Related

Problems with updating pfgplots inside docker with tds file structure

I have a docker image with texlive installed (via apt not tlmgr). I have a pgfplot in my project which needs a newer pgfplot version. I'm searching for ways to update my pgplots because I can't update it with tlmgr because of base install via apt.
Initial error message if I try to compile with texlive 2014:
! Package pgfkeys Error: Choice '1.16' unknown in choice key '/pgfplots/compat/
anchors'. I am going to ignore this key.
See the pgfkeys package documentation for explanation.
Type H <return> for immediate help.
...
l.7 \pgfplotsset{compat=1.16}
?
! Emergency stop.
...
l.7 \pgfplotsset{compat=1.16}
I downloaded the pgfplots.tds and did the following steps like the manual said:
docker cp pgfplots.tds docker_container_name:/root/texmf/pgfplots
export TEXINPUTS=/root/texmf/pgfplots/tex//:
export TEXDOCS=/root/texmf/pgfplots/doc//:
export LUAINPUTS=/root/texmf/pgfplots//:
texhash
Of course the export and texhash were done inside the container and not on the host system.
After this, the error message is gone, but I have a new issue:
package pgfplots notification 'compat/show suggested version=true': you might b
enefit from \pgfplotsset{compat=1.18} (current compat level: 1.16).
! Illegal parameter number in definition of \pgfmaththisrow#.
<to be read again>
I searched online and got the response that this is because of a broken pgfplots installation. In many articles the fix was just to install the texlive new. But I can't do that.
The issue should also not be in the tex code itself. If I install texlive on my host system, which is the most recent Ubuntu distro, the tex compiles just fine.
Can somebody help me in fixing this or lead me to a better way of upgrading pgfplots?
Resolution:
The pgfplots package 1.18.1 and also 1.16 were to recent. It had conflicts with the pgf package. I tried to go further back and landed on \pgfplotsset{1.14} and version 1.14 of pgfplots.tds.
This works fine now. I was probably pretty lucky that my plot looks and functions the same with this version as in 1.18.
This approach probably won't work for you if your more bound to version 1.18.

Unable to run 'tcl' file on Vivado 2016.4 version

I am trying to run a .tcl file originally configured for 2014.4 on 2016.4 version of Vivado. However I am getting the following error:
while executing
"create_bd_cell -type ip -vlnv xilinx.com:ip:mig mig_0 "
(procedure "create_root_design" line 111)
invoked from within
"create_root_design """
(file "all.tcl" line 405)
The tcl file uses the part 'xcku040-ffva1156-2' and tries to access the IP 'mig' which I believe is renamed/changed on later versions. Is there any workaround for this?
Steps I have done till now:
Changed the version number to 2016.4
tried replacing target boards.
tried on the same board with an alternate IP for mig.
tried on both 2016.4 and 2015.4 versions
None of these have worked so far
Attaching the '.tcl' file for reference : all.tcl
Since with every version upgrade of the Vivado Design Suite, parts are renamed or removed, it is not possible to run a .tcl file meant for an earlier version in newer releases. So I ran the above query on Xilinx Community Forums and found a workaround:
Run this script on the previous version(2014 in this case), generate the design and then open the same design using the next major release(2015 version). The 2015 version will automatically suggest upgrades to the discontinued/renamed IPs. Repeat the same to get to 2016 version. That's the only way to get this done. Also have to keep checking if the core functionality of the IP is the same after automated upgrades by Vivado Design Suite.

Installing VIM in Minix 3.1.8

I've Googled this a thousand times and I cannot, for the life of me, get VIM to work on my Minix 3. For the record, I am running on a Windows machine with Minix 3 working on Oracle's VM VirtualBox.
I've tried typing,
# pkgin up && pkgin in vim
but I get the error:
pkgin: Can't open database /usr/var/db/pkgin/pkgin.db: unable to open database file: No such file or directory
I then try to do pkgin search git to search for a package, but I get the same error. Could this be some kind of Internet connection issue? I'm incredibly confused.
If you haven't already, download the binary package from here:
ftp://ftp.minix3.org/pub/minix/packages/3.3.0/i386/editors/
Change "i386" to your correct architecture, if different.
As you're probably already familiar, this page tells you how to install binary packages for Minix:
http://wiki.minix3.org/en/UsersGuide/InstallingBinaryPackages
As far as your "pkgin" errors, here are two possible solutions:
http://osdir.com/ml/minix3/2011-03/msg00244.html
How to install vim into Minix3?
I asked on the Minix 3 Google Groups Forums and they solved my problem. If anyone else has trouble, I'm pasting a response by Lionel:
Switch to http downloads by editing "/usr/pkg/etc/pkgin/repositories.conf" and comment out the line:
ftp://ftp.minix3.org/pub/minix/packages/$osrelease/$arch/All
and add the following:
http://www.minix3.org/pkgsrc/packages/$osrelease/$arch/All
Then do shutdown, boot, pkgin update and then install your desired packages.

Running hh_client on one file hangs forever

I used the build instructions from this link
centos install docs
It seemed to install fine. I ran hhvm --version
HipHop VM 3.5.0-dev+2014.12.11 (rel)
Compiler: heads/master-0-g546087bf1b0560c4a9e254fcad46a9212e42ccc2
Repo schema: cf1780b3cc3857e091e924935ae6267e9794de9c
Extension API: 20140829
So following the bootstrapping docs I create a directory with 2 files (test.php and .hhconfig)
I added the following code to test.php
<?hh
function f(): int {
return 'not an int';
}
f();
In this directory i run hh_client and the following message appears for a long time 20-30mins+. Is this normal? I tried using a docker container with hhvm already and installed and got the same behavior.
This might be a known problem: can you do killall -9 hh_server; export USER=$(logname) before trying again? If that fixes it, you've hit an issue I just fixed this week in https://github.com/facebook/hhvm/commit/53b4d9b1ad7ccf99ef7b80d5d673f1578c9791c8. That fix should be in the latest nightly build, so if you update your build, that might fix it too.
If not, it sounds like you've set it up correctly. Please file a bug at https://github.com/facebook/hhvm/issues and I'll work with you on looking into it. StackOverflow isn't really the right forum for debugging like this.

Bower not copying any files

Im using bower as part of the yeoman 1.0 beta 4 install. All looks well however when I run bower install I get the expected output yet no files are copied to app/components as advertised.
I am running on windows which I understand is not officially supported yet. Has any one managed to get this up and running with some success? I have followed some tutorials on line relating to the subject however I think they are out dated. I managed to install yeoman without any additional steps and no errors as far as I can tell.
Grunt File being Used
Oh no... Git was not on the system path. Adding it caused me to run into another small error with a solution found here http://wingkaiwan.com/2012/11/25/bower-errors-on-windows/
Thank you Mr Ricky Wan

Resources