Hi Sean,
The command line worked, but I had to redo the commands:
Riesling:/ dulci$ export OCSSWROOT=/Applications/seadas-7.3.1/ocssw/
Riesling:/ dulci$ source $OCSSWROOT/OCSSW_bash.env
Because the first time I tried to cd into $OCSSWROOT/run/scripts it told me the folder didn't exist. It DID exist this morning. :confused:
But I have a .GEO file now for my L1A_LAC.
And the modis_L1B processor worked from the GUI.
And so did the l2gen with the default settings. Excellent.
Now I have to go look into how to change the default parameters for cloud cover.
Thank you again. If there is a way to fix the GUI modis_GEO, that would be great, but if not now I know how to run it from the command line and it will work.
-dulci
L1A to modis_geo to L1B problem
-
OB.DAAC - SeanBailey
- User Services
- Posts: 1470
- Joined: Wed Sep 18, 2019 6:15 pm America/New_York
- Been thanked: 5 times
L1A to modis_geo to L1B problem
Glad it's working :grin:
Unless you set the environment in your .bashrc it will only live as long as the terminal window does, so that probably explains why you needed to reset it.
We are finalizing an update to the GUI to resolve the https connection issues within the JAVA code (and add some new features).
At that time, the installer script will be able to be run from the GUI again - and perhaps that will solve your GUI running issues. ...but I think it should just work now...
Sean
Unless you set the environment in your .bashrc it will only live as long as the terminal window does, so that probably explains why you needed to reset it.
We are finalizing an update to the GUI to resolve the https connection issues within the JAVA code (and add some new features).
At that time, the installer script will be able to be run from the GUI again - and perhaps that will solve your GUI running issues. ...but I think it should just work now...
Sean