[Rock-dev] [rock] #181: Yaml Config files are broken under ruby1.9 and a german system

[rock]

#181: Yaml Config files are broken under ruby1.9 and  a german system
-----------------------+-----------------------------------
 Reporter:  jama01     |      Owner:  rock-dev-mailing-list
     Type:  defect     |     Status:  new
 Priority:  blocker    |  Milestone:
Component:  toolchain  |   Keywords:
-----------------------+-----------------------------------
 If one uses ruby1.9 together with an german system
 the yaml parsing of the config files is broken.
 This results in wrongly configured components.

 Only double values seem to be broken :
 Orocos.rb : Configuration.rb
 doc = doc.join("")
 result = YAML.load(StringIO.new(doc))
 puts("result #{result} #{doc}")

 Doc:
 "# cost above which the search is aborted\n",
   "cost_cutoff: 1000000.0\n",
   "# no documentation available for this property\n",
   "enable_known_unknown_filter: 0\n",
   "# no documentation available for this property\n",
   "enable_narrow_wide_filter: 0\n",
   "# no documentation available for this property\n",
   "enable_strong_edge_filter: 0\n",
   "# no documentation available for this property\n",
   "known_unknown_filter: \n",
   "  unknown_class: 0\n",
   "# the band name in the traversability map that should be used as the
 underlying data\n",
   "map_band: \"\"\n",
   "# the map ID of the traversability map that should be used for
 planning\n",
   "map_id: /corridor_planner/traversability\n",
   "# when using an on-disk envire environment, this is the path to the
 environment. Otherwise, leave empty and send the map through the map input
 port.\n",
   "map_path: \"\"\n",
   "# allowed cost margin, as a rate w.r.t. the optimal cost (i.e. 1.1
 means 10% above optimal)\n",
   "margin: 1.1\n",
   "# minimum width at which a corridor can be traversed, in meters\n",
   "min_width: 0.0\n",
   "# no documentation available for this property\n",
   "narrow_wide_filter: \n",
   "  narrow_threshold: 0.0\n",
   "  wide_threshold: 0.0\n",
   "# starting point in world coordinates\n",
   "start_point: \n",
   "  data: \n",
   "  - 6.95325192721126e-310\n",
   "  - 1.30537677e-316\n",
   "  - 6.92301922937865e-310\n",
   "# no documentation available for this property\n",
   "strong_edge_filter: \n",
   "  env_path: \"\"\n",
   "  map_id: \"\"\n",
   "  band_name: \"\"\n",
   "  threshold: 6.92301126802583e-310\n",
   "# target point in world coordinates\n",
   "target_point: \n",
   "  data: \n",
   "  - 6.9532519272089e-310\n",
   "  - 6.9230192352588e-310\n",
   "  - 0.0\n",
   "# path to the terrain class definition file\n",
   "terrain_classes: \"\"\n"
 result:
 {cost_cutoff => 1000000.0, enable_known_unknown_filter => 0,
 enable_narrow_wide_filter => 0, enable_strong_edge_filter => 0,
 known_unknown_filter => {unknown_class => 0}, map_band => , map_id =>
 /corridor_planner/traversability, map_path => , margin => 1.0, min_width
 => 0.0, narrow_wide_filter => {narrow_threshold => 0.0, wide_threshold =>
 0.0}, start_point => {data => [6.0, 1.0, 6.0]}, strong_edge_filter =>
 {env_path => , map_id => , band_name => , threshold => 6.0}, target_point
 => {data => [6.0, 6.0, 0.0]}, terrain_classes => }

 As a workaround one can set
 export LANG="C"
 prior to starting any script.

-- 
Ticket URL: <http://rock.opendfki.de/ticket/181>
rock <http://rock.opendfki.de>
rock: the robot construction kit