You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and files (although very small ones are generated for me at /tmp/pytest-of-root/pytest-1/test-data0/simtools-simulate-prod-gamma_20_deg/simtools-output/test-production//simtel-data/North/gamma/data/run000002_gamma_za020deg_azm000deg_North_TestLayout_test-production.simtel.zst
The log files look reasonable and it runs through without errors.
There are issues, many statements like
Warning: problematic transmission between telescope and observation level.
Evaluation was between observation layer at 21.560000 m a.s.l.
and 31.000000 m above, plus 16.000000 m in the telescope.
Lookup in transmission table in wavelength range from 200 to 1000 nm,
altitude range from 2.156000 to 100.000000 km a.s.l.,
for wavelength 400 nm from 0.052560 km a.s.l., for airmass factor 1.000000
Starting altitude of 0.052560 km is out of range (2.156000 to 100.000000 km).
This is either an underground installation or the wrong transmission table.
At 400 nm we get a transm. of 0.000000 between tel. and obs.lev., and 0.000000 inside tel.
Your transmission table might not be appropriate for the given site.
We are ignoring this problematic part now but you should fix your set-up.
Was this resolved in the meantime? The original PR does not refer to this issue again and a search for these warnings does not appear anywhere else in the repo. Therefore I am opening this issue so that we remember to check it.
The text was updated successfully, but these errors were encountered:
Tried to remember and reread the issues / pull requests, but seems we didn't address this (multiple points were addressed).
This is a good point and I actually suggested / wanted to suggest that we move all those test functions from test_applications_from_config.py to a separate test module. This would be cleaner and allow us as well to write unit tests on this code.
Originally posted by @GernotMaier in #875 (comment)
Was this resolved in the meantime? The original PR does not refer to this issue again and a search for these warnings does not appear anywhere else in the repo. Therefore I am opening this issue so that we remember to check it.
The text was updated successfully, but these errors were encountered: