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

Use kadi dynamic commanded states for starcheck thermal model #330

Merged
merged 8 commits into from
Jul 17, 2019

Conversation

jeanconn
Copy link
Contributor

@jeanconn jeanconn commented Jul 12, 2019

Use kadi dynamic commanded states for starcheck thermal model

Closes #329

Supersedes #319

@jeanconn
Copy link
Contributor Author

@taldcroft I think this is all looking good, but what would you like to see as documentation of testing for both the PR and for LR?

As we've changed

  • method of getting states for continuity interval
  • handling of eclipses (from none to some handling)
  • determination of initial state with temperature from telemetry

I'm not sure if each needs to be validated independently or if "acq and guide temps for a set of schedules match expectations" is enough.

@taldcroft
Copy link
Member

Showing that "acq and guide temps for a set of schedules match expectations" is enough, where of course the set of schedules includes a couple with eclipses.

@jeanconn
Copy link
Contributor Author

jeanconn commented Jul 12, 2019

Regarding eclipses, I suppose I can use the proseco pkl files for straightforward independent determination of those expectations (I had just been going "oh that's different and probably right due to eclipse").

@taldcroft
Copy link
Member

Or use one of the eclipse loads that failed starcheck but passed FOT thermal, and show now passing. I would approve that.

@jeanconn jeanconn force-pushed the run_start_plus_kadi branch from 31b9233 to 6d180c1 Compare July 14, 2019 15:21
starcheck/src/starcheck.pl Outdated Show resolved Hide resolved
starcheck/src/starcheck.pl Outdated Show resolved Hide resolved
@jeanconn
Copy link
Contributor Author

jeanconn commented Jul 14, 2019

Regarding the states in general, I was happy to see the temperatures matched the MCC/pkl ones much better for the eclipse schedules, though I wasn't sure if we should add eclipse to the starcheck aca thermal model plot.

I also thought these were close to the mcc values but not quite as close as I would have guessed.

jun1019a_diff
jun1719a_diff
jun2419a_diff

(and I still had an action to try to understand what is happening in the beginning of JUN1719A)

@taldcroft
Copy link
Member

Re eclipse checking, looks great, I'll call that a pass!

@jeanconn jeanconn force-pushed the run_start_plus_kadi branch from 6d180c1 to b1bc7d1 Compare July 16, 2019 18:31
@jeanconn jeanconn force-pushed the run_start_plus_kadi branch from b1bc7d1 to 6be87a5 Compare July 16, 2019 18:37
starcheck/calc_ccd_temps.py Outdated Show resolved Hide resolved
@taldcroft
Copy link
Member

Code looks good now, thanks! Just need to re-run the validation plots and standard regression.

@jeanconn
Copy link
Contributor Author

Regarding standard regression, I ran with the "-3" run_start_time vs current master (not release) and get text diffs that look reasonable to me, with temperature differences that look up to 0.1 deg on first scroll-through:

regress_diffs.txt

@jeanconn
Copy link
Contributor Author

In more review it looks like there are some larger temperature diffs. I notice some in JAN1215B which should have eclipses in it. I would prefer to do more rigorous eval of the diffs (and confirm that all larger diffs are due to eclipses) but I think basically we are OK and any reasonable diffs related to temperature are fine. We're mostly using the full regression set to just confirm that everything runs and there are no new weird errors.

@jeanconn
Copy link
Contributor Author

For the validation plots, I ran these with these start times

./sandbox_starcheck -dir kadistates/jun1019a/ -out jun1019a_kadi -run_start_time 2019:155:14:00:00.000
./sandbox_starcheck -dir kadistates/jun1719a/ -out jun1719a_kadi -run_start_time 2019:162:22:00:00.000
./sandbox_starcheck -dir kadistates/jun2419a/ -out jun2419a_kadi -run_start_time 2019:169:00:00:00.000

./sandbox_starcheck -dir kadistates/mar2519a/ -out mar2519a_kadi -run_start_time '2019:079:22:00:00.000'
./sandbox_starcheck -dir kadistates/mar1119b/ -out mar1119b_kadi -run_start_time '2019:065:18:00:00.000'

And rerun of the weeks and their plots comparing to the pickle temperatures look the same

jun1019a_diff
jun1719a_diff
jun2419a_diff
mar1119b_diff
mar2519a_diff

@jeanconn jeanconn changed the title Run_start_time plus kadi states Use kadi dynamic commanded states for starcheck thermal model Jul 17, 2019
@jeanconn
Copy link
Contributor Author

@taldcroft Is this officially good to go now?

Copy link
Member

@taldcroft taldcroft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent!!

@jeanconn jeanconn merged commit 12950b6 into master Jul 17, 2019
@jeanconn jeanconn deleted the run_start_plus_kadi branch July 17, 2019 15:29
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

Successfully merging this pull request may close these issues.

2 participants