Autocurator =========== ``Autocurator`` is an optional tool for scanning data. In some test cases it has shown to be faster than the Python-centric approach of using ``Xarray``. In the default workflow ``esgpublish`` uses a subprocess to call the executable over each input file then open its output in ``.json`` format. Additional it can be called in custom workflows using the individual CLI publishing modules. Install ------- If you do not wish to install autocurator via conda, the option also exists to clone and install it from git:: git clone http://github.com/sashakames/autocurator.git cd autocurator make After running this, there should be an autocurator executable saved as ``.../autocurator/bin/autocurator``. You will need to update the config if you choose to do this with the correct path to the autocurator folder, as the default is just the ``autocurator`` command. Running Autocurator ------------------- Before running ``autocurator`` (if you are not using the conda installed version) you must first run the following command:: export LD_LIBRARY_PATH=$CONDA_PREFIX/lib This command helps autocurator locate and open shared libraries within the current conda environment. It will not work if this is not run. This also goes for running the ``esgpublish`` command if, in your config, you have listed a direct path instead of simply the autocurator command. If you want to run ``autocurator`` as a stand alone, use the following format:: bash autocurator.sh The executable itself can also be run like so:: bin/autocurator --out_pretty --out_json --files However, this mode is sometimes difficult as specifying multiple files requires using a ``dir/*.nc`` format which sometimes causes issues. Overall, we recommend using the script above as it cleans up a few things. You can also use the conda install as above, but the path/command will just be "autocurator". Once you have your scan file, you can use that to run ``esgmkpubrec`` (see that page for more info).