SeaDAS 8.3 install-OCSSW problem on Mac

Use this Forum to find information on, or ask a question about, NASA Earth Science data.
Post Reply
hwaga
Posts: 3
Joined: Mon Jul 19, 2021 5:55 pm America/New_York
Answers: 0

SeaDAS 8.3 install-OCSSW problem on Mac

by hwaga » Sat Jul 01, 2023 9:42 pm America/New_York

I'm struggling with an error installing OCSSW tools for SeaDAS 8.3. When I run "./install_ocssw --install_dir $HOME/ocssw --tag V2022.3 --seadas --modisa --seawifs" on terminal, I get the following error message:

>> ./install_ocssw --install_dir $HOME/ocssw --tag V2022.3 --seadas --modisa --seawifs
Traceback (most recent call last):
File "/Users/main/SeaDAS/./install_ocssw", line 1004, in <module>
sys.exit(run())
File "/Users/main/SeaDAS/./install_ocssw", line 954, in run
bundleInfo["dir"] = "bin" # fix the install directory
TypeError: 'NoneType' object does not support item assignment

The same issue happens when I try on SeaDAS desktop app, i.e., SeaDAS-ToolboX>Install/Update SeaDAS Processors.

Here is my Softwere % System Info:

-----------------------------------------------------------
Main Application Platform:
-----------------------------------------------------------
Application Version: SeaDAS 8.3.0
SNAP Engine Version: 9.0.3* (SeaDAS Platform modified)
SNAP Desktop Version: 9.0.3* (SeaDAS Platform modified)
SNAP Engine Build Date: 202212081832
SNAP Desktop Build Date: 202212081837
Installation Directory: /Users/main/SeaDAS
Data Directory: /Users/main/.seadas8
Configuration: /Users/main/SeaDAS/etc/snap.properties
VM Configuration: /Users/main/SeaDAS/etc/seadas.conf
WARNING!! File '/Users/main/SeaDAS/etc/seadas.conf' does not exist
VM Configuration: /Users/main/SeaDAS/etc/snap.conf
WARNING!! File '/Users/main/SeaDAS/etc/snap.conf' does not exist
VM Configuration (gpt): /Users/main/SeaDAS/bin/gpt.vmoptions
VM Configuration (pconvert): /Users/main/SeaDAS/bin/pconvert.vmoptions
Runtime Configuration: /Users/main/.seadas8/etc/snap.properties
Runtime Configuration (SeaDAS Toolbox): /Users/main/.seadas8/etc/seadas.properties
JRE: Java(TM) SE Runtime Environment 1.8.0_201-b09
JVM: Java HotSpot(TM) 64-Bit Server VM by Oracle Corporation
Memory: 3641 MiB
OCSSWROOT (Java Env): null
Python3 Directory: /Users/main/.pyenv/shims/python3


-----------------------------------------------------------
SeaDAS Toolbox:
-----------------------------------------------------------
SeaDAS Toolbox Version: 1.3.0
SeaDAS Toolbox Build Date: 202212081844
Configuration: /Users/hwaga/.seadas8/etc/seadas.properties
OCSSW Root Directory: /Users/main/Analysis/Seadas/ocssw
OCSSW Log Directory: /
OCSSW Location: local
Environment {$OCSSWROOT} (external): null


-----------------------------------------------------------
NASA Science Processing (OCSSW):
-----------------------------------------------------------
WARNING! Cannot find 'seadas_info' in the OCSSW bin directory



-----------------------------------------------------------
General System and Software (from GUI):
-----------------------------------------------------------

Operating System: Mac OS X 10.16
Java Version: 1.8.0_201

Tags:

OB SeaDAS - xuanyang02
Subject Matter Expert
Subject Matter Expert
Posts: 656
Joined: Tue Feb 09, 2021 5:42 pm America/New_York
Answers: 1
Been thanked: 2 times

Re: SeaDAS 8.3 install-OCSSW problem on Mac

by OB SeaDAS - xuanyang02 » Mon Jul 03, 2023 11:26 am America/New_York

Can you do

Code: Select all

echo $HOME

Code: Select all

echo $OCSSWROOT
Also, try to run ./install_ocssw in the same directory with install_ocssw and manifest.py you downloaded.

Code: Select all

./install_ocssw --install_dir /Users/hwaga/ocssw  --tag V2022.3 --seadas --modisa --seawifs

OB SeaDAS - xuanyang02
Subject Matter Expert
Subject Matter Expert
Posts: 656
Joined: Tue Feb 09, 2021 5:42 pm America/New_York
Answers: 1
Been thanked: 2 times

Re: SeaDAS 8.3 install-OCSSW problem on Mac

by OB SeaDAS - xuanyang02 » Thu Jul 27, 2023 2:21 pm America/New_York

We were able to replicate the error you encountered. It seems that adding /usr/local/bin to your PATH in your .bashrc or .bash_profile would work, if you use bash.

Post Reply