Upadate of transit spectra calculator#57
Conversation
|
I checked the tests and I am not sure if I broke the unit tests or not because to me they seem unrelated to my changes. @AaronDavidSchneider could you have a look at it? |
|
I raised this as an issue in the h5py repo. Lets see if they reply. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #57 +/- ##
==========================================
+ Coverage 78.30% 78.65% +0.34%
==========================================
Files 14 14
Lines 1549 1593 +44
==========================================
+ Hits 1213 1253 +40
- Misses 336 340 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
Got it to work! Thanks again @AaronDavidSchneider for your help with the h5py problems. |
AaronDavidSchneider
left a comment
There was a problem hiding this comment.
looks good to me! Thanks @Kiefersv
There was a problem hiding this comment.
in an ideal world, we would add these hardcoded values in the test to the test configuration in test_gcmtools_common.py
There was a problem hiding this comment.
... but I am also fine keeping it like this.
|
There is something wired in the test values, i will have closer look |
|
any update @Kiefersv? |
Hey all,
I updated the transit spectrum calculator. Instead of using a fixed longitudinal opening angle for all latitudes, it now uses a coordinate transformation to average over the full terminator grid cell, even a the pols.
I still need to adjust the tests, but the code is arleady tested and should work.