It has come to my attention that some of our JSON infrastructure does not correctly name resources relative to the OPENRAVE_DATA path (these files exist in the pr_ordata package, so this is the correct way to reference them). Nobody should be passing around OPENRAVE_DATA paths explicitly -- it is up to packages to advertise their ordata/data directories correctly (which pr_ordata does, with the help of openrave_catkin).
According to @mkoval, there are two types of problems:
JSON files are not loaded relative to the OPENRAVE_DATA path. When a JSON file is to be loaded, its actual filesystem path should be resolved using openravepy.RaveFindLocalFile() (like all other such resources are loaded).
The JSON files themselves reference other files with hardcoded paths, instead of paths relative to OPENRAVE_DATA.
I'm also tagging @Shushman and @jeking04 because they were discussing this briefly today.
It has come to my attention that some of our JSON infrastructure does not correctly name resources relative to the
OPENRAVE_DATApath (these files exist in thepr_ordatapackage, so this is the correct way to reference them). Nobody should be passing aroundOPENRAVE_DATApaths explicitly -- it is up to packages to advertise theirordata/datadirectories correctly (whichpr_ordatadoes, with the help ofopenrave_catkin).According to @mkoval, there are two types of problems:
OPENRAVE_DATApath. When a JSON file is to be loaded, its actual filesystem path should be resolved usingopenravepy.RaveFindLocalFile()(like all other such resources are loaded).OPENRAVE_DATA.I'm also tagging @Shushman and @jeking04 because they were discussing this briefly today.