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 pp jet id correct #25

Merged

Conversation

istaslis
Copy link

@istaslis istaslis commented Dec 1, 2015

Removed JetID for pp data sequence

istaslis added a commit that referenced this pull request Dec 1, 2015
@istaslis istaslis merged commit 37c6e6d into CmsHI:forest_CMSSW_7_5_5_patch4 Dec 1, 2015
@harmonicoscillator
Copy link

@istaslis please make sure that you update makeJetSequences.sh so that they re-create the jet sequences you have edited here. DO NOT edit the jet sequences by hand, they should only ever come from the makeJetSequences script.

@istaslis
Copy link
Author

istaslis commented Dec 1, 2015

@richard-cms good comment! In fact I did it like following:

  • updated templateSequence_bTag_cff.py.txt
  • ran makeJetSequences.sh
  • then I had to checkout elder versions of HiReRecoJets_pp_cff.py, HiReRecoJets_HI_cff.py, HiGenJets_cff.py because they are made incorrectly (to be fixed in future I guess)

the problem is that github cannot show differences in more than 300 files so you probably haven't seen template changes in PR comparison. As an idea we can remove all sequences from git and remake sequences after checkout the branch... It would simplify version control.

@harmonicoscillator
Copy link

@istaslis okay great, sounds like everything is fine then.

Yes, HiReRecoJets_pp_cff.py, HiReRecoJets_HI_cff.py, HiGenJets_cff.py have been messed up for a while, but at least those are not the sequences.

I think that we should not force users to run the script at compile time, that will confuse a lot of people. I agree this GitHub limitation is very annoying.

@istaslis
Copy link
Author

istaslis commented Dec 1, 2015

@richard-cms what about something like this? ;)
https://www.digitalocean.com/community/tutorials/how-to-use-git-hooks-to-automate-development-and-deployment-tasks
and we can add then sequences to .gitignore file

not sure we should do it, but as an idea.

@harmonicoscillator
Copy link

I would be very much in favor of using hooks if this was a regular git repo that we were using. Unfortunately CMSSW uses this pre-built CMSSW base versions and sparse checkouts, and we merge a special branch in to do HiForest development. I have been toying with the idea of splitting off just the HeavyIonsAnalysis package into a separate git repo just for that package (instead of a CMSSW branch) and in that case maybe we should use hooks. This definitely won't happen during the run though.

@istaslis
Copy link
Author

istaslis commented Dec 1, 2015

thanks for checking possible ideas! git submodules is a great idea too!

@harmonicoscillator
Copy link

People seem to hate git submodules: https://codingkilledthecat.wordpress.com/2012/04/28/why-your-company-shouldnt-use-git-submodules/
(among many, many other similar articles)

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