local input files in working node instead of reading them from EOS #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eters, storage area, and input LHE file entry
…GM and XRoot commands
…os and xarea vars plus better comments
…nts and header/footer
local input files in working node instead of reading them from EOS
correcting misprint in headers of generate scripts for all years
merging changes from remote
diemort
added a commit
that referenced
this pull request
Oct 18, 2023
local input files in working node instead of reading them from EOS
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The improvement of running on local input files by copying them from EOS avoids permissions errors and slow I/O from EOS. Additional comments and header/footer have been added to all files. Usual commands have been replaced with XRoot commands to interact with EOS interface.
second flow after rebase