Problems encountered by modis_L1A.py in processing moids L0 data

Please enter here to ask a question about any NASA Science related topics!
geoding
Posts: 8
Joined: Thu Mar 04, 2021 8:38 am America/New_York

Problems encountered by modis_L1A.py in processing moids L0 data

by geoding » Thu Mar 04, 2021 9:21 am America/New_York

I am using modis_L1A.py to process moids L0 data and encounter the following error message
ionput:MODOOF.A2015137.1415.20151380602.001.PDS
output:A2015137.1415.20151380602.L1A_LAC
“execution exception: java.io.lOException: modis_LlA.py failed with exit codeCheck log for more details.”

Tags:

OB SeaDAS - aynur
Subject Matter Expert
Subject Matter Expert
Posts: 34
Joined: Tue Dec 20, 2011 12:28 pm America/New_York

Re: Problems encountered by modis_L1A.py in processing moids L0 data

by OB SeaDAS - aynur » Thu Mar 04, 2021 9:49 am America/New_York

Please let us know which version of SeaDAS you are using.

Thanks,
Aynur

geoding
Posts: 8
Joined: Thu Mar 04, 2021 8:38 am America/New_York

Re: Problems encountered by modis_L1A.py in processing moids L0 data

by geoding » Fri Mar 05, 2021 1:28 am America/New_York

it is SeaDAS 7.5.3

OB SeaDAS - xuanyang02
Subject Matter Expert
Subject Matter Expert
Posts: 133
Joined: Tue Feb 09, 2021 5:42 pm America/New_York

Re: Problems encountered by modis_L1A.py in processing moids L0 data

by OB SeaDAS - xuanyang02 » Fri Mar 05, 2021 3:29 pm America/New_York

Do you have terra installed? One way to find out is to click OCSSW->update data processors. You should have terra grayed out and the checkbox underneath terra checked. If not, you should check that checkbox and then click run.

Bing

geoding
Posts: 8
Joined: Thu Mar 04, 2021 8:38 am America/New_York

Re: Problems encountered by modis_L1A.py in processing moids L0 data

by geoding » Sat Mar 06, 2021 8:56 am America/New_York

Sincerely thank you for your help, I have installed terra before and also updated the update data processors. But still the previous error




thanks,
ding

gnwiii
Posts: 606
Joined: Fri Jan 29, 2021 5:51 pm America/New_York
Answers: 1

Re: Problems encountered by modis_L1A.py in processing moids L0 data

by gnwiii » Sat Mar 06, 2021 11:25 am America/New_York

The mentioned log files may already be present and can be attached to a post.

Are you running "modis_L1A.py" from the GUI? Using the command line, you can run "modis_L1A.py --help" to see the command-line options, which include creating log files and more verbose (detailed) output that might explain the problem.

geoding
Posts: 8
Joined: Thu Mar 04, 2021 8:38 am America/New_York

Re: Problems encountered by modis_L1A.py in processing moids L0 data

by geoding » Sun Mar 07, 2021 12:15 am America/New_York

thanks!
I am implementing the OCSSW->modis_L1A option in seadas-7.5.3 in order to process modis L0 data. I have checked that there is a modis_L1A.py file in the /seadas-7.5.3/OCSSW/scripts/ path. The detailed processing log is as follows:
"
2021/03/07 11:36:17
server ocssw root path: /home/ding/seadas-7.5.3/ocssw/scripts
Debugging: added property name: file
Debugging: added property name: cancel
Debugging: added property name: geofile
Debugging: added property name: ifile
Debugging: added property name: --output
Debugging: added property name: --output
Debugging: added property name: geofile
Debugging: added property name: --mission
Debugging: property changed from to STARTNUDGE
Debugging: added property name: --startnudge
Debugging: property changed from to STOPNUDGE
Debugging: added property name: --stopnudge
Debugging: property changed from to NEXT
Debugging: added property name: --nextgranule
Debugging: added property name: --log
Debugging: added property name: --disableL0fix
Debugging: added property name: file
Debugging: added property name: --output
Debugging: added property name: --mission
Debugging: added property name: --startnudge
Debugging: added property name: --stopnudge
Debugging: added property name: --nextgranule
Debugging: added property name: --log
Debugging: added property name: --verbose
Debugging: added property name: --disableL0fix
Debugging: added property name: RUN_BUTTON_STATUS_CHANGED
Debugging: added property name: geofile
Debugging: added property name: infile
Debugging: primary io file option names: file --output
Debugging: set param value: file /home/ding/data/modis/003/MOD00F.A2015137.1415.20151380602.001.PDS
Debugging: file /home/ding/data/modis/003/MOD00F.A2015137.1415.20151380602.001.PDS
Debugging: command array content: /home/ding/seadas-7.5.3/ocssw/scripts/ocssw_runner --ocsswroot /home/ding/seadas-7.5.3/ocssw get_obpg_file_type.py /home/ding/data/modis/003/MOD00F.A2015137.1415.20151380602.001.PDS
Debugging: Running the program [Ljava.lang.String;@7f0f1a18
Debugging: command array content: /home/ding/seadas-7.5.3/ocssw/scripts/ocssw_runner --ocsswroot /home/ding/seadas-7.5.3/ocssw next_level_name.py /home/ding/data/modis/003/MOD00F.A2015137.1415.20151380602.001.PDS modis_L1A.py
Debugging: Running the program [Ljava.lang.String;@39e3534e
error stream: Unable to determine time stamp for input file /home/ding/data/modis/003/MOD00F.A2015137.1415.20151380602.001.PDS
Debugging: property changed from to A
Debugging: added property name: --mission
Debugging: added property name: --startnudge
Debugging: added property name: --stopnudge
Debugging: added property name: --nextgranule
Debugging: added property name: --log
Debugging: added property name: --disableL0fix
Debugging: primary io file option names: file --output
Debugging: set param value: --output
Debugging: --output
Debugging: property changed from to /home/ding/seadas-7.5.3/
"
Attachments
Processing window.png
Processing window.png (103.33 KiB) Not viewed yet

gnwiii
Posts: 606
Joined: Fri Jan 29, 2021 5:51 pm America/New_York
Answers: 1

Re: Problems encountered by modis_L1A.py in processing moids L0 data

by gnwiii » Mon Mar 08, 2021 11:20 am America/New_York

I'm not sure if modis_L1A.py can work with files that are more than one 5-minute granule (some documents mention a 2-hour limit for PDS files) or if it is confused by the change in day number. Does modis_timestamp work? Maybe your file is corrupt. There may be more information in the log files.

OB SeaDAS - xuanyang02
Subject Matter Expert
Subject Matter Expert
Posts: 133
Joined: Tue Feb 09, 2021 5:42 pm America/New_York

Re: Problems encountered by modis_L1A.py in processing moids L0 data

by OB SeaDAS - xuanyang02 » Mon Mar 08, 2021 12:22 pm America/New_York

Thanks for posting the log here. Unfortunately, next_name_level.py used by GUI has a little trouble to work with the file name of MODOOF.A2015137.1415.20151380602.001.PDS from LAADS.

To work around that, I have two suggestions:
1) run modis_L1A.py on command line:
"/home/ding/seadas-7.5.3/ocssw/scripts/modis_L1A.py MODOOF.A2015137.1415.20151380602.001.PDS" in the directory you store your data /home/ding/data/modis/003/
or
2)download MOD00.A2015137.1415_1.PDS.bz2 from our site https://oceandata.sci.gsfc.nasa.gov/MOD ... /2015/137/, unzip it, and run modis_L1A on GUI with MOD00.A2015137.1415_1.PDS as input. Please make sure you choose T instead of A for mission.

Bing

geoding
Posts: 8
Joined: Thu Mar 04, 2021 8:38 am America/New_York

Re: Problems encountered by modis_L1A.py in processing moids L0 data

by geoding » Fri Mar 12, 2021 9:50 pm America/New_York

thank you very much,
I tried your suggestion and unfortunately I received the following error message---stderror.I don't know what to do.
"
ava.util.concurrent.ExecutionException: java.io.IOException: modis_L1A.py failed with exit code 1.
Check log for more details.
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at javax.swing.SwingWorker.get(SwingWorker.java:602)
at gov.nasa.gsfc.seadas.processing.common.CallCloProgramAction$4.done(CallCloProgramAction.java:252)
at javax.swing.SwingWorker$5.run(SwingWorker.java:737)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.run(SwingWorker.java:832)
at sun.swing.AccumulativeRunnable.run(AccumulativeRunnable.java:112)
at javax.swing.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(SwingWorker.java:842)
at javax.swing.Timer.fireActionPerformed(Timer.java:313)
at javax.swing.Timer$DoPostEvent.run(Timer.java:245)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Caused by: java.io.IOException: modis_L1A.py failed with exit code 1.
Check log for more details.
at gov.nasa.gsfc.seadas.processing.common.CallCloProgramAction$4.doInBackground(CallCloProgramAction.java:241)
at gov.nasa.gsfc.seadas.processing.common.CallCloProgramAction$4.doInBackground(CallCloProgramAction.java:212)
at com.bc.ceres.swing.progress.ProgressMonitorSwingWorker.doInBackground(ProgressMonitorSwingWorker.java:55)
at javax.swing.SwingWorker$1.call(SwingWorker.java:295)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at javax.swing.SwingWorker.run(SwingWorker.java:334)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)


"
Attachments
seadas processing software installer.png
seadas processing software installer.png (24.69 KiB) Not viewed yet
modis_L1A processor.png
modis_L1A processor.png (24.21 KiB) Not viewed yet
Last edited by geoding on Sat Mar 13, 2021 7:13 am America/New_York, edited 1 time in total.

Post Reply