When do_holes == True, then get_reflected_1d is called with input optical properties representing a clear-sky atmosphere. Possible issue is that this call takes in the CLOUDY variants of GCOS2, ftau_cld, and ftau_ray.
This may have been intentional, but maybe not. I don't understand these terms enough to know for sure.
To test if it was a bug I did the following experiment:
- Computed a reflected light spectrum where I never called
inputs.clouds.
- Computed a reflected light spectrum where I called
inputs.clouds, but with do_holes=True, fhole=1.0 and fthin_cld=0.0
These two calculations do not produce the same result (even though intuition says they should), suggesting it is possibly a bug.
|
GCOS2[:,:,ig],ftau_cld[:,:,ig],ftau_ray[:,:,ig], |
When
do_holes == True, thenget_reflected_1dis called with input optical properties representing a clear-sky atmosphere. Possible issue is that this call takes in the CLOUDY variants ofGCOS2,ftau_cld, andftau_ray.This may have been intentional, but maybe not. I don't understand these terms enough to know for sure.
To test if it was a bug I did the following experiment:
inputs.clouds.inputs.clouds, but withdo_holes=True,fhole=1.0andfthin_cld=0.0These two calculations do not produce the same result (even though intuition says they should), suggesting it is possibly a bug.
picaso/picaso/justdoit.py
Line 330 in 1930fc8