Skip to content

Conversation

@mikemhenry
Copy link
Contributor

No description provided.

@dwhswenson dwhswenson changed the title add needed assets for showcase notebook add fetch subcommand for showcase notebook Jun 5, 2023
@codecov
Copy link

codecov bot commented Jun 5, 2023

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (501aded) 91.13% compared to head (0857807) 91.14%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #437   +/-   ##
=======================================
  Coverage   91.13%   91.14%           
=======================================
  Files         106      106           
  Lines        6241     6244    +3     
=======================================
+ Hits         5688     5691    +3     
  Misses        553      553           
Impacted Files Coverage Δ
openfecli/fetchables.py 100.00% <100.00%> (ø)
openfecli/tests/test_fetchables.py 100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

mikemhenry and others added 2 commits June 5, 2023 15:32
Co-authored-by: David W.H. Swenson <david.swenson@omsf.io>
@mikemhenry mikemhenry marked this pull request as ready for review June 5, 2023 23:38
@mikemhenry mikemhenry requested a review from dwhswenson June 5, 2023 23:38
@mikemhenry mikemhenry changed the title add fetch subcommand for showcase notebook add fetch subcommand for showcase notebook inputs Jun 5, 2023
@mikemhenry mikemhenry changed the title add fetch subcommand for showcase notebook inputs add fetchables for showcase notebook inputs Jun 5, 2023
@mikemhenry
Copy link
Contributor Author

@dwhswenson ready for review 🎉
Right now it works for the getting the showcase on binder, I don't want it to pull down the notebook since with the way it is setup, the notebook + files pulled down won't work together.

@mikemhenry
Copy link
Contributor Author

Also once this gets merged in, I will need to cut a new release + make a new installer for our colab installer


from openfecli.fetching import URLFetcher, PkgResourceFetcher

_EXAMPLE_NB_BASE = ("https://raw.githubusercontent.com/"
Copy link
Contributor

Choose a reason for hiding this comment

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

If we change the url here to be against a tag/commit then we can't accidentally break these. If we are patching the files, it makes more sense to be intentional about updating this url to reflect that.

Copy link
Member

Choose a reason for hiding this comment

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

@richardjgowers: Is the intent for try.openfree.energy to only update on releases? Like, a typo fix in notebook will only be reflected on a release of openfe?

If we do that, I'd recommend setting up some automation to check that that this is the most up-to-date. "Be intentional about updating the URL" sounds to me like "we're going to forget to update the URL."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

With the installer hard-coded + the URL using a tagged release, then we are pretty set in keeping try.openfree.energy stable. Even if we push a new release and have API changes, the notebook will still be using the "old" installer, so it will stay stable and just have to remember to update it.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes I think try. should be off releases not HEAD


from openfecli.fetching import URLFetcher, PkgResourceFetcher

_EXAMPLE_NB_BASE = ("https://raw.githubusercontent.com/"
Copy link
Member

Choose a reason for hiding this comment

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

@richardjgowers: Is the intent for try.openfree.energy to only update on releases? Like, a typo fix in notebook will only be reflected on a release of openfe?

If we do that, I'd recommend setting up some automation to check that that this is the most up-to-date. "Be intentional about updating the URL" sounds to me like "we're going to forget to update the URL."

],
short_name="rbfe-showcase",
short_help="Inputs needed for the RBFE Showcase Notebook",
section="Tutorials",
Copy link
Member

Choose a reason for hiding this comment

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

Seems to me that, without the actual notebook, this is only intended for internal use. If so, change the section name (to anything, really, but I default to using "hidden") so that it doesn't show in help.

@mikemhenry
Copy link
Contributor Author

We should hold off merging this until people are happy with OpenFreeEnergy/ExampleNotebooks#69 (just in case I need to make changes to this PR)

@richardjgowers richardjgowers merged commit ff410fd into main Jun 12, 2023
@richardjgowers richardjgowers deleted the feat/add_showcase_to_fetch branch June 12, 2023 09:22
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.

4 participants