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

Fix stated temperature range of atoMEC #209

Merged
merged 1 commit into from
Oct 11, 2023

Conversation

timcallow
Copy link
Contributor

Relates to issue #147 . The temperature range stated in the warning now matches that which triggers the warning

@codecov
Copy link

codecov bot commented Oct 11, 2023

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (ad0aea7) 96.63% compared to head (bf51b55) 97.09%.
Report is 1 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #209      +/-   ##
===========================================
+ Coverage    96.63%   97.09%   +0.45%     
===========================================
  Files           14       14              
  Lines         2407     2407              
===========================================
+ Hits          2326     2337      +11     
+ Misses          81       70      -11     
Files Coverage Δ
atoMEC/check_inputs.py 95.35% <ø> (+2.78%) ⬆️

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@timcallow timcallow merged commit b8042f0 into atomec-project:develop Oct 11, 2023
5 checks passed
@timcallow timcallow deleted the warnings_improve branch October 11, 2023 11:16
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.

1 participant