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

Trim Perl dependencies by moving more to Python #348

Merged
merged 15 commits into from
Jul 15, 2020
Merged

Conversation

jeanconn
Copy link
Contributor

@jeanconn jeanconn commented Jul 5, 2020

Description

Trim Perl dependencies by moving more to Python.

Specifically, this removes the rather heavy PDL dependency and also cuts the various time-related dependencies.
It also seemed time to move a bunch of Python into starcheck.utils to make it easier to call from multiple pieces of the Perl.

It also just removes the Dark Cal Checker.

Testing

Passes unit tests on MacOS, linux, Windows (at least one required) No unit tests

  • Functional testing - ran sandbox_starcheck on several recent loads from Linux without errors
  • Regression testing - ran on Linux and see only expected changes (all dark cal reporting is gone)

@jeanconn jeanconn changed the title WIP: Trim Perl dependencies by moving more to Python Trim Perl dependencies by moving more to Python Jul 10, 2020
@jeanconn
Copy link
Contributor Author

jeanconn commented Jul 10, 2020

My thought regarding the Dark Cal checker is that we can either run an old version of starcheck in a pinch or resurrect the Perl module if we go back to doing those activities.

@jeanconn jeanconn requested a review from taldcroft July 14, 2020 02:41
@taldcroft
Copy link
Member

My thought regarding the Dark Cal checker is that we can either run an old version of starcheck in a pinch or resurrect the Perl module if we go back to doing those activities.

I'm good with cutting the dark cal checker. It is extremely unlikely we will go back to doing cals that way.

@jeanconn
Copy link
Contributor Author

Great! And yeah, I figured it was fine to cut but figured I'd talk it out in PR just like we have.

starcheck/src/starcheck.pl Outdated Show resolved Hide resolved
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.

I'm +:100: on this PR. Awesome work. All I request is more documentation of the functional testing. Not every single result and diffs etc, but up to a few sentence description of what functional tests were run and how results were evaluated.

raise ValueError("Float run_start_time should be negative")
return ref_time.date
from starcheck.pcad_att_check import check_characteristics_date
from starcheck.utils import (_make_pcad_attitude_check_report,
Copy link
Member

Choose a reason for hiding this comment

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

YES!!!! Excellent idea.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Well, it was your idea and it was a good one! So much nicer to keep the Python in a separate file and just convenient for editing. I think some of the exception handling and wrappers still need simplification and improvement, but moving them into the separate file is a good start.

@jeanconn
Copy link
Contributor Author

Terrific. What would you like to see for functional testing? And indeed I should have documented. Right now I've run on recent test loads and it runs in ska3 and makes output. Since making the PR, I've also run the old complete regression test set and they run without issue (functional component) and the output looks good with the only diffs being that all the dark cal checker output is correctly missing (regression tests pass).

@taldcroft
Copy link
Member

Sounds good.

@jeanconn jeanconn merged commit 184f220 into master Jul 15, 2020
@jeanconn jeanconn deleted the more_modernize branch July 15, 2020 18:02
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