l2gen MOD02/MYD02
-
- Posts: 23
- Joined: Mon Apr 24, 2017 4:08 pm America/New_York
l2gen MOD02/MYD02
Hello,
I am actually working with MOD02HKM/MOD02QKM and MYD02HKM/MYD02QKM on SeaDAS 7.4.
I've downloaded MODIS images on https://ladsweb.modaps.eosdis.nasa.gov/
I am trying to apply l2gen on these images and it doesn't work.
There is a warning message : ## WARNING!! file /home/cnormandin/MODIS images/MOD02HKM.A2016015.1155.006.201601519461.hdf is not a valid input mission : Mission=null
Thank you in advance,
Cassandra Normandin
I am actually working with MOD02HKM/MOD02QKM and MYD02HKM/MYD02QKM on SeaDAS 7.4.
I've downloaded MODIS images on https://ladsweb.modaps.eosdis.nasa.gov/
I am trying to apply l2gen on these images and it doesn't work.
There is a warning message : ## WARNING!! file /home/cnormandin/MODIS images/MOD02HKM.A2016015.1155.006.201601519461.hdf is not a valid input mission : Mission=null
Thank you in advance,
Cassandra Normandin
Tags:
-
- Subject Matter Expert
- Posts: 259
- Joined: Thu Mar 05, 2009 10:25 am America/New_York
- Been thanked: 2 times
l2gen MOD02/MYD02
For processing MODIS with l2gen, ifile needs the 1KM file and you can set resolution to 500 or 250 to process at HKM or QKM. You will also need the geolocation file.
This will process your example file at HKM:
l2gen ifile=MOD021KM.A2016015.1155.006.2016015194614.hdf geofile=MOD03.A2016015.1155.006.2016015190344.hdf ofile=T2016015115500.L2_LAC_OC.nc resolution=500
Files need:
MOD03.A2016015.1155.006.2016015190344.hdf
MOD021KM.A2016015.1155.006.2016015194614.hdf
MOD02HKM.A2016015.1155.006.2016015194614.hdf (to process at 500 or 250)
MOD02QKM.A2016015.1155.006.2016015194614.hdf (to process at 250)
don
This will process your example file at HKM:
l2gen ifile=MOD021KM.A2016015.1155.006.2016015194614.hdf geofile=MOD03.A2016015.1155.006.2016015190344.hdf ofile=T2016015115500.L2_LAC_OC.nc resolution=500
Files need:
MOD03.A2016015.1155.006.2016015190344.hdf
MOD021KM.A2016015.1155.006.2016015194614.hdf
MOD02HKM.A2016015.1155.006.2016015194614.hdf (to process at 500 or 250)
MOD02QKM.A2016015.1155.006.2016015194614.hdf (to process at 250)
don
-
- Posts: 23
- Joined: Mon Apr 24, 2017 4:08 pm America/New_York
-
- Posts: 23
- Joined: Mon Apr 24, 2017 4:08 pm America/New_York
l2gen MOD02/MYD02
Hello don,
I've written this post few weeks ago about l2gen process on MODIS Terra/Aqua MOD021KM/MYD021KM. It worked well without problem.
Last week it worked well too. But until this morning, a warning message appears saying ".... is not a valid input mission: Mission=null". I did exactly the same process than before, even with the same images of the last week, it doesn't work this time. I don't understand why.
Thank you in advance,
Cassandra
I've written this post few weeks ago about l2gen process on MODIS Terra/Aqua MOD021KM/MYD021KM. It worked well without problem.
Last week it worked well too. But until this morning, a warning message appears saying ".... is not a valid input mission: Mission=null". I did exactly the same process than before, even with the same images of the last week, it doesn't work this time. I don't understand why.
Thank you in advance,
Cassandra
-
- Subject Matter Expert
- Posts: 278
- Joined: Mon Apr 07, 2008 4:40 pm America/New_York
l2gen MOD02/MYD02
Hi Cassandra,
We can better help you if you post the exact full command you are running, if you are in fact running this from the command line.
If you are running this from the SeaDAS visualization package, let us know this along with describing the exact steps in order for us to replicate what you are doing.
Also if this worked for you last week and does not work now for the exact same command and the exact same files, has something changed on your machine during this time frame? Have you updated OCSSW during this time frame?
thanks
Danny
We can better help you if you post the exact full command you are running, if you are in fact running this from the command line.
If you are running this from the SeaDAS visualization package, let us know this along with describing the exact steps in order for us to replicate what you are doing.
Also if this worked for you last week and does not work now for the exact same command and the exact same files, has something changed on your machine during this time frame? Have you updated OCSSW during this time frame?
thanks
Danny
-
- Posts: 23
- Joined: Mon Apr 24, 2017 4:08 pm America/New_York
l2gen MOD02/MYD02
Hi Danny,
Thank you for your reply.
I am working with the SeaDAS gui. For example, I am using the next files :
- MOD021KM.A2013191.1015.006.2014220154608.hdf
- MOD03.A2013191.1015.006.2013191172659.hdf
The only thing I made until the last week is to click on "yes" on the message that appears when I start SeaDAS "SeaDAS is about on-line check for a new softwarer version. Do you want SeaDAS to perform the on-line version check now?"
Then, in l2gen, I choose my ifile : MOD021KM.A2013191.1015.006.2014220154608.hdf. The warning message appears "file... is not a valid input mission: Mission=null" and I can't do anything else. A colleague who has installed the lask week SeaDAS has the same problem.
Thank you again,
Cassandra
Thank you for your reply.
I am working with the SeaDAS gui. For example, I am using the next files :
- MOD021KM.A2013191.1015.006.2014220154608.hdf
- MOD03.A2013191.1015.006.2013191172659.hdf
The only thing I made until the last week is to click on "yes" on the message that appears when I start SeaDAS "SeaDAS is about on-line check for a new softwarer version. Do you want SeaDAS to perform the on-line version check now?"
Then, in l2gen, I choose my ifile : MOD021KM.A2013191.1015.006.2014220154608.hdf. The warning message appears "file... is not a valid input mission: Mission=null" and I can't do anything else. A colleague who has installed the lask week SeaDAS has the same problem.
Thank you again,
Cassandra
l2gen MOD02/MYD02
Have you rebooted the system or logged in to a new session since
Such problems can be tricky to detect using a GUI. In a terminal, try entering
Once you have done that, you should get a version from
l2gen
was last working? A new login generally resets environment variables, so it is possible some variables are being set incorrectly and the l2gen
that fails is an old version or you have the right version but it are using an old OCSSWROOT
directory. Such problems can be tricky to detect using a GUI. In a terminal, try entering
$ l2gen |head -1
(the "$
" is the bash "input prompt"; you only type the portion of line following the prompt and then "return" or "enter"). You should see either l2gen: command not found
or l2gen 8.10.3-r0 (Mar 9 2017 15:31:51
. If you get l2gen: command not found
, try entering $ echo XX$OCSSWROOT
. If you get a response of just XX
, you need to set the OCSSWROOT
environment variable and then source a small script to adust the PATH
variable and set locations of the data directories, etc. To do that, enter something like the following 2 lines (you may need to adjust the paths for your configuration):export OCSSWROOT=$HOME/seadas-7.4/ocssw
. $OCSSWROOT/OCSSW_bash.env
Once you have done that, you should get a version from
$ l2gen |head -1
-
- Posts: 23
- Joined: Mon Apr 24, 2017 4:08 pm America/New_York
l2gen MOD02/MYD02
Thank you for your answer.
Ok I've just XX as answer. When I've opened the terminal, a message appears saying "bash: home/cnormandin/seadas-7.4/ocssw/OCSSW_bash.env : no file"
I'm trying to do what you said.
Thank you,
Cassandra
Ok I've just XX as answer. When I've opened the terminal, a message appears saying "bash: home/cnormandin/seadas-7.4/ocssw/OCSSW_bash.env : no file"
I'm trying to do what you said.
Thank you,
Cassandra
-
- Posts: 23
- Joined: Mon Apr 24, 2017 4:08 pm America/New_York
l2gen MOD02/MYD02
Ok. I've done what you said.
Now, I've the version "l2gen 8.10.3-r0 (Mar 9 2017 15:31:51).
But I've the same problem with the l2gen GUI "WARNING.. file is not a valid input mission: Mission=null"
Now, I've the version "l2gen 8.10.3-r0 (Mar 9 2017 15:31:51).
But I've the same problem with the l2gen GUI "WARNING.. file is not a valid input mission: Mission=null"
l2gen MOD02/MYD02
The first step in solving your problem is to get the current
(
For example:
This adds
If you don't see helpful message, you can attach the log file to a forum post (first write the post and save it, then attach the log file). I have attached the log
for the above example so you can compare with your own test.attachment 1
l2gen
running in the terminal (it is easier to cut and paste between forum messages and the terminal than to write down all the steps used in the GUI). The next step is to try processing your file from the command-line. Change to the directory that has your input (
MOD02?KM.A...
and MOD03.A...
) files and enter the l2gen
command as suggested in Don's initial response:$ l2gen ifile=MOD021KM.A<your_specs>.hdf geofile=MOD03.A<your_specs>.hdf ofile=AYYYYDDDTTTTTT.L2_LAC_OC.nc resolution=500 2>&1 > l2gen.log
For example:
$ l2gen ifile=MYD021KM.A2013191.1015.006.2013192153330.hdf geofile=MYD03.A2013191.1015.006.2013192150551.hdf ofile=A2013191101500.L2_LAC_OC.nc resolution=500 2>&1 > l2gen.log
This adds
2>&1 > l2gen.log
after Don's example to save the output in a log file. You can view l2gen.log
in an editor or in the terminal using:$ less l2gen.log
If you don't see helpful message, you can attach the log file to a forum post (first write the post and save it, then attach the log file). I have attached the log
for the above example so you can compare with your own test.attachment 1