Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

run_tetracorder.sh no output and no clear error messages #11

Open
ksegl opened this issue Feb 13, 2024 · 2 comments
Open

run_tetracorder.sh no output and no clear error messages #11

ksegl opened this issue Feb 13, 2024 · 2 comments

Comments

@ksegl
Copy link

ksegl commented Feb 13, 2024

Hi,
I tried to test the emit-sds-l2b software but without success so far. I did the following:
First, I installed:

  • tetracorder5.26
  • emit-sds-l2b and emit-utils
    Second, I transformed the provided
  • EMIT_L2A_RFL_001_20240129T090901_2402906_020.nc
  • EMIT_L2A_RFLUNCERT_001_20240129T090901_2402906_020.nc
    to ENVI BIL format as it seems to be a requirement.

Third, I run the run_tetracoder.sh script that was adapted to my data and configuration:

setenv TETRA_CMDS /opt/spectroscopy-tetracorder/t1/tetracorder.cmds/tetracorder5.26e.cmds
setenv TETNCPU 8

sh run_tetracorder.sh /misc/min4/EMIT/TEST/results_karl /misc/min4/EMIT/TEST/results_karl/ag /misc/min4/EMIT/TEST/EMIT_ref.bil /misc/min4/EMIT/TEST/EMIT_ref_unc.bil /misc/min4/EMIT/emit-utils /misc/min4/EMIT/emit-sds-l2b /opt/spectroscopy-tetracorder/t1/tetracorder.cmds/tetracorder5.26e.cmds >& logfile

The logfile and the cmd.runtet.out show no error messages except that the tetracoder processing was much too fast. Error messages can only be found in the tetracorder.out file that is attached.
Unfortunately, I can't do anything with these messages. Can somebody help? Thanks!

cmd.runtet.out.txt
logfile.txt
run_tetracorder.sh.txt
tetracorder.out.txt

@unbohn
Copy link

unbohn commented Feb 29, 2024

@pgbrodrick Could you perhaps take a look at this if time permits?

@pgbrodrick
Copy link
Contributor

The current run_tetracorder.sh is mostly to give a sense of a type of implementation...the exact environment and run setup is a little different now...see the actual implementation here:

https://github.com/emit-sds/emit-main/blob/6e8441ef22463e74d66339df113b13125f73963b/emit_main/workflow/l2b_tasks.py#L71

Noting in particular the environment references.

@ksegl , you can see the relevant errors towards the end of cmd.runtet.out.txt. It looks like the input file is bad....run_tetracorder.sh makes some assumptions about the ENVI extensions, specifically that the binary has no extension and the header matches that binary with a .hdr. Adjusting either the filename of your .bil, or modifying the tetracorder.sh should help sort that out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants