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 up the uproot getting started #486

Merged
merged 1 commit into from
Nov 1, 2022
Merged

Conversation

gordonwatts
Copy link
Collaborator

Update the uproot query in getting started:

  • Use OpenData
  • Use a more sophisticated query to help ease user into best practices

@gordonwatts gordonwatts self-assigned this Oct 30, 2022
@codecov
Copy link

codecov bot commented Oct 30, 2022

Codecov Report

Base: 91.15% // Head: 91.15% // No change to project coverage 👍

Coverage data is based on head (d36c2b5) compared to base (71bb598).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #486   +/-   ##
========================================
  Coverage    91.15%   91.15%           
========================================
  Files           11       11           
  Lines          226      226           
  Branches         6        6           
========================================
  Hits           206      206           
  Misses          16       16           
  Partials         4        4           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

@gordonwatts gordonwatts added bug Something isn't working docs Documentation enhancement New feature or request labels Oct 30, 2022
import awkward as ak

dataset_name = [
"https://xrootd-local.unl.edu:1094//store/user/AGC/nanoAOD/nanoaod15.root"

Choose a reason for hiding this comment

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

While I am not aware of any intention of moving this file, I am wondering whether in the longer term it would be safer to use scikit-hep-testdata (or an IRIS-HEP version of such a repository). A potential issue of the file disappearing would be alleviated by CI of course that could catch it when it happens.

Copy link
Contributor

Choose a reason for hiding this comment

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

Strong agree here.

Copy link
Contributor

@BenGalewsky BenGalewsky left a comment

Choose a reason for hiding this comment

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

Seems more robust too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working docs Documentation enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants