ningking1986 / geotop

Automatically exported from code.google.com/p/geotop
0 stars 0 forks source link

Error building path for input files #1

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. compile "matteo" branch
2. run geotop on a directory *different* from the directory containing the 
input files

What is the expected output? What do you see instead?

geotop should run without issues. Instead, it raises an error:

[E] MeteoIO: 
**** backtrace ****
    (1) in mio::FileNotFoundException::FileNotFoundException(std::string const&, std::string const&) from /home/antonio/zurich/usecases/meteoio/lib/libmeteoio.so.2  [0x7f3cb867d9c9]+0x79
    (2) in mio::ARCIO::read2DGrid_internal(mio::Grid2DObject&, std::string const&) from /home/antonio/zurich/usecases/meteoio/lib/libmeteoio.so.2  [0x7f3cb86a02e5]+0x15f5
    (3) in mio::ARCIO::readDEM(mio::DEMObject&) from /home/antonio/zurich/usecases/meteoio/lib/libmeteoio.so.2  [0x7f3cb86a17a9]+0x169
    (4) in mio::IOHandler::readDEM(mio::DEMObject&) from /home/antonio/zurich/usecases/meteoio/lib/libmeteoio.so.2  [0x7f3cb864ec3f]+0x8f
    (5) in mio::BufferedIOHandler::readDEM(mio::DEMObject&) from /home/antonio/zurich/usecases/meteoio/lib/libmeteoio.so.2  [0x7f3cb866a645]+0x175
    (6) at ./geotop/geotop() [0x5370c4]
    (7) at ./geotop/geotop() [0x45482e]
    (8) at ./geotop/geotop() [0x43bf4b]
    (9) in __libc_start_main from /lib/x86_64-linux-gnu/libc.so.6  [0x7f3cb7a05ea5]+0xf5
    (10) at ./geotop/geotop() [0x407799]
[ARCIO.cc:177] FileNotFoundException: ./input_maps/pit.asc

Please use labels and text to provide additional information.

This is probably due to the fact that the current WORKING_DIRECTORY is not 
added to the path of the configuration file in the various values in the Config 
object.

A possible way to fix this is to override configuration options in Config 
object, when they correspond to specific files. However, I don't know what are 
the paths that should be changed, if there is an "official" list or we can just 
check for strings ending in "PATH".

Original issue reported on code.google.com by antonio....@gmail.com on 30 Sep 2013 at 9:18

GoogleCodeExporter commented 9 years ago
This has been fixed . 

Original comment by stefano....@exact-lab.it on 10 Nov 2013 at 8:11