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

Update env #333

Merged
merged 4 commits into from
Apr 8, 2020
Merged

Update env #333

merged 4 commits into from
Apr 8, 2020

Conversation

maxnoe
Copy link
Member

@maxnoe maxnoe commented Apr 8, 2020

No description provided.

@codecov
Copy link

codecov bot commented Apr 8, 2020

Codecov Report

Merging #333 into master will increase coverage by 0.70%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #333      +/-   ##
==========================================
+ Coverage   42.88%   43.59%   +0.70%     
==========================================
  Files          70       69       -1     
  Lines        4694     4618      -76     
==========================================
  Hits         2013     2013              
+ Misses       2681     2605      -76     
Impacted Files Coverage Δ
lstchain/scripts/lstchain_data_muon_analysis.py

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7422c50...9946216. Read the comment docs.

@maxnoe maxnoe mentioned this pull request Apr 8, 2020
rlopezcoto
rlopezcoto previously approved these changes Apr 8, 2020
@maxnoe
Copy link
Member Author

maxnoe commented Apr 8, 2020

@rlopezcoto sorry, I pushed another commit, you'll need to approve again

yrenier added a commit to cta-sst-1m/cta-lstchain that referenced this pull request Apr 8, 2020
@@ -40,10 +40,16 @@ def find_scripts(script_dir, prefix):
packages=find_packages(),
py_modules='version',
install_requires=[
'astropy',
Copy link
Contributor

Choose a reason for hiding this comment

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

this is going to install the latest astropy (4.0), right?

Copy link
Member Author

Choose a reason for hiding this comment

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

It's the same as in the environment file (no version specification).

If astropy is already installed in any version, it won't update, if it is not installed it will install the latest version.

Copy link
Contributor

Choose a reason for hiding this comment

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

I was wondering whether we would need to implement any modification if this was required (as it was done in ctapipe), but I guess that Travis is testing it now with 4.0 since we are not specifying anything, right?

Copy link
Member Author

@maxnoe maxnoe Apr 8, 2020

Choose a reason for hiding this comment

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

looking into the log, astropy 3.2 is installed

Copy link
Member Author

Choose a reason for hiding this comment

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

That is a bit strange. Seems it's because of conda-forge.

Copy link
Contributor

Choose a reason for hiding this comment

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

ok, shall we merge this and open another one forcing astropy 4.0 in case there are some things that need to be modified?

Copy link
Member Author

Choose a reason for hiding this comment

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

yes

@maxnoe maxnoe merged commit cc51d7e into cta-observatory:master Apr 8, 2020
@maxnoe maxnoe deleted the update_env branch April 8, 2020 12:57
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