Start Page

Getting Started with Nutria

Using Nutria via Web Interface

How to run a webserver locally is up to the user. We provide an option to do so with a simple python script located in the bin directory of the HydroVish installation, which can be run as follows:

  • Navigate to HydroVish\bin\win64. If you don't know where your HydroVish installation is, right-click on your desktop shortcut for HydroVish and select "Open file location"
  • Run python HydroVishNutriaServer.py to start the webservice on your machine
  • Note: Make sure you have Python installed. If you are using Windows and have an MSYS terminal, you can do this by running pacman -Syuu python.

    If you don't want to use Python, there are more sophisticated options for running a webserver such as Apache. If this is used, it must be configured in a way that allows calling HydroVish via CG scripting.

    Navigate to the link shown in your command line in a browser, e.g. http://localhost:8080/HydroVish.exe. You now have an instance of HydroVish/Nutria running in your browser.

  • Select a converter, and configure all the necessary parameters and output options.
  • When you're ready, click the "Process" button in the third column.
  • This will automatically launch the interface.

    Using Nutria via Command Line

    To invoke HydroVish as command line tool via the Nutria API, the two environment variables REQUEST_METHOD and QUERY_STRING need to be set. Such can be done conveniently via a Makefile. However, a Query String is still needed, so until further development of an easier method, one must use the Web Interface to build the desired Query String.

    The makefile will then look as follows:


    
    	export REQUEST_METHOD=GET
    	export QUERY_STRING=...
    
    	HydroVish=C:/home/myUser/vish/bin/win64/HydroVish
    
    	run:
    		$(HydroVish)
    	

    Where QUERY_STRING is followed by the Query String you've generated with the Web Interface or otherwise. It needs to be encoded according to the standard of the CGI. To encode a URl, there are tools such as urlencoder.org.

    Save this as "Makefile", and run mingw32-make on the directory you saved it to.


    Below are examples of different ways of creating a makefile with gmake to convert one or several SDC files to F5. Their complexity is in incremental order, so it is recommended to start with 1. convertSingleSDC to understand how to build makefiles for your processes.

    Note: The paths in these sample makefiles are set relative to AirborneHydroMapping/HydroVish/data/SampleData/FWF, so you must have the SampleData downloaded with your HydroVish installer.

    1. convertSingleSDC
    2. convertSingleSDC-via-gmake-functions
    3. convertMultipleSDC-via-gmake
    4. convertMultipleSDC-via-gmake-simplified
    5. convertMultipleSDC-via-gmake-functions
    6. convertMultipleSDC-via-Nutria-function
    7. convertAllSDC
    8. convertAllSDC-with-InstalledHydroVish
    9. importTrajectory
    10. convertScannerToWorldCoordinates
    11. convertAllSDC-with-Installed-HydroVish
    12. convertToWorldAndRefragment


    Start Page