dyld: Library not loaded

[OB SeaDAS - knowles]

Depending on how you launch SeaDAS, if via clicking on the icon to launch it, then you will need to first restart your computer in order for your edits to take effect.

Also when you are in the SeaDAS GUI, check under menu OCSSW -> Update OC Processors   Does the directory match your command line path?
/Applications/seadas-7.4/ocssw

Does this return?
$ get_obpg_file_type.py /Users/Tulay/Desktop/MODIS_Ehux/Sampling_Days_L1_L2/A2017175103500.L1B_LAC
A2017175103500.L1B_LAC: MODIS Aqua: Level 1B

Or does it return?
$ get_obpg_file_type.py /Users/Tulay/Desktop/MODIS_Ehux/Sampling_Days_L1_L2/A2017175103500.L1B_LAC

A2017175103500.L1B_LAC: MODIS Aqua: Level 1B

The first blank line as shown in one of your posts would pose a problem.

Also check your .profile for any sort of line print commands

Danny

[tcokacar]

Depending on how you launch SeaDAS, if via clicking on the icon to launch it, then you will need to first restart your computer in order for your edits to take effect.

-no change after restarting the computer

Also when you are in the SeaDAS GUI, check under menu OCSSW -> Update OC Processors   Does the directory match your command line path?
/Applications/seadas-7.4/ocssw

-Yes the command line path matches.

Does this return?
$ get_obpg_file_type.py /Users/Tulay/Desktop/MODIS_Ehux/Sampling_Days_L1_L2/A2017175103500.L1B_LAC
A2017175103500.L1B_LAC: MODIS Aqua: Level 1B

Or does it return?
$ get_obpg_file_type.py /Users/Tulay/Desktop/MODIS_Ehux/Sampling_Days_L1_L2/A2017175103500.L1B_LAC

A2017175103500.L1B_LAC: MODIS Aqua: Level 1B

The first blank line as shown in one of your posts would pose a problem.

-It returns without any blank
$ get_obpg_file_type.py /Users/Tulay/Desktop/MODIS_Ehux/Sampling_Days_L1_L2/A2017175103500.L1B_LAC
A2017175103500.L1B_LAC: MODIS Aqua: Level 1BAlso check your .profile for any sort of line print commands

Also check your .profile for any sort of line print commands
-I haven't have any .profile file.

Thanks Tulay

[OB SeaDAS - knowles]

Something is not configured right.  What happens if you launch SeaDAS from the command line?

Open a terminal window.

Verify that you get:
$ get_obpg_file_type.py /Users/Tulay/Desktop/MODIS_Ehux/Sampling_Days_L1_L2/A2017175103500.L1B_LAC
A2017175103500.L1B_LAC: MODIS Aqua: Level 1B

Then launch seadas:
$ open /Applications/seadas-7.4/bin/seadas.app &

Does the GUI for l2gen now recognize the ifile A2017175103500.L1B_LAC ?

Danny

[OB SeaDAS - knowles]

Note: I corrected SeaDAS GUI launch directory path in my last post:

Correct for your case is:
$ open /Applications/seadas-7.4/bin/seadas.app &

[tcokacar]

Thanks Danny,

I did the checks and launch seadas from the command line ($ open /Applications/seadas-7.4/bin/seadas.app &).  Still, the GUI for l2gen does not recognize the ifile A2017175103500.L1B_LAC.

Tülay

[OB SeaDAS - knowles]

I'm running out of ideas.  Hopefully other forum users will have some suggestions.

There are 3 possible configuration files:  ~/.bash_profile , ~/.bash_login , and ~/.profile .   Perhaps back all these up and create new ones removing anything which might be questionable.  Mostly you need your PATH defined and make sure it includes your anaconda python.

Also reinstall SeaDAS and maybe do it in a directory other than Applications.  Then install OCSSW. 

Basically try to get a clean install on a clean machine as best you can. 

Note: we have tested SeaDAS on Sierra but not High Sierra, so I don't know if that is an issue.

Danny

[gnwiii]

I don't have access to High Sierra, but some things to consider:

1. debugging problems such as you encountered can be a lot of work and are best done on by experienced users on systems that are not crtical for other tasks,

2. changes in SIP -- some things that worked in earlier versions may be blocked bu SIP in High Sierra.  For security reasons, disabling SIP to use SeaDAS is not a solution, but could be useful in a test (preferably using an alternate system disk that will be wiped after the tests have been made) to eliminate SIP as a contributing factor to the problem.

3. macOS provides extensive logs, so there is a good chance that you could find clues in the logs.  The problem is that the logs are so extensive that it can be hard to isolate a problem.
You should start from a fresh boot, run the GUI l2gen test and note the time when the error occurs, then use the console app to look for errors around the time l2gen fails.

[tcokacar]

Dear All,

Thank you for your kind guides. I could not relaunch the Seadas 7.4 since my internet access was limited at that time and had trouble to download OCSSW. So I could not test latest suggestions.

Anyway, I have high speed internet connection now and download updated version of Seadas (7.5). The problem is over :))

Thanks a lot
Tulat