Page 1 of 1
An issue in processing MODIS L1A to L1B
Posted: Thu Oct 26, 2017 2:18 pm America/New_York
by alsahli
Hi there,
I am using fedora 26 (64bit) and SeaDAS7.4. I encountered an issue when trying to process MODIS L1A to LB1 is that modis_LB1.py could not recognize the geo file generated by modis_GEO.py. I got this message:
[img]Screenshotfrom2017-10-2621-03-41.png[/img]
Thanks in advance,
Mohammad
An issue in processing MODIS L1A to L1B
Posted: Fri Oct 27, 2017 10:33 am America/New_York
by OB SeaDAS - dshea
Yes, it seems there is a bug with the filename guessing logic in the GUI. For now just run the programs on the command line:
modis_GEO.py A2013237033500.L1A_LAC.x.hdf
modis_L1B.py A2013237033500.L1A_LAC.x.hdf
An issue in processing MODIS L1A to L1B
Posted: Fri Oct 27, 2017 10:54 am America/New_York
by alsahli
Thanks for the replay,
Where can I use these commands?
Are these commands written in the terminal or in a certain place in SeaDAS.
Any hint would be highly appreciated!
Mohammad
An issue in processing MODIS L1A to L1B
Posted: Fri Oct 27, 2017 7:36 pm America/New_York
by gnwiii
The commands Sean posted are meant to be entered in a terminal. If you are not familiar with the bash shell (fedora linux and macOS both use the same bash shell program), My comments in
the ocssw installation thread apply equally well to fedora.
An issue in processing MODIS L1A to L1B
Posted: Sat Oct 28, 2017 10:30 pm America/New_York
by OB SeaDAS - knowles
The "x" in the name "A2013237033500.L1A_LAC.x.hdf" is unfortunately fooling the modis_L1B GUI. We will look into fixing this autonaming issue in the future.
If you take a step back and look at your run of modis_GEO from the GUI you will notice that when you loaded your input file "A2013237033500.L1A_LAC.x.hdf" it autonamed your output GEO file as "A2013237033500.GEO.x.hdf". This is correct.
I'm assuming you kept that name and ran it.
Next when you next loaded "A2013237033500.L1A_LAC.x.hdf" into the modis_L1B GUI as the ifile this GUI tried to autoname the GEO file as "A2013237033500.GEO.hdf". This is incorrect. Notice that the "x" towards the end of the filename did not carry over in this GUI. So no match.
Currently to get this to work in the GUI you have 2 choices.
Choice 1. Use the multilevel_processor and it will correctly autoname everything for you and carry the "x" along with each filename.
... or Choice 2. Rename the file to "A2013237033500.L1A_LAC.hdf" then both modis_GEO and modis_L1B GUI will work.
Note: your multilevel_processor parameters will look something like this:
[main]
ifile=/yourfilepath/A2013237033500.L1A_LAC.x.hdf
[modis_L1B.py]
keepfiles=1
[geo]
keepfiles=1
hope this helps,
Danny