Add CMS Getting Started for AOD, MiniAOD, NanoAOD

[jmhogan]

This PR adds docs pages for CMS AOD, MiniAOD, and NanoAOD formats, addressing several tasks in #3452.

• cernopendata/modules/fixtures/data/docs/cms-getting-started-aod/ will replace the cms-getting-started-2010 and cms-getting-started-2011 pages
• cernopendata/modules/fixtures/data/docs/cms-getting-started-miniaod/ will replace the cms-getting-started-2015 page
• cernopendata/modules/fixtures/data/docs/cms-getting-started-nanoaod/ is a new addition

Please forgive the inevitable first-time-contributor gaffs!

Some of the contents of these pages refer to records that will be made in the future. Hopefully all links are currently valid, but several should updated with new records before new CMS documentation are records are put into production. (#3495, #3496, #3537, #3281, #3279)

This slightly addresses #3465 by no longer linking to these older records as examples.

[katilp]

If I'm not wrong the standard mkedanlz does not produce code that works in CMSSW_10_6_30. It is not the container feature but the release feature: it includes objects that are not in the standard miniaod (and also does not produce the config file). A mention of that could be added. A work-through attempt is reported in the GitLab issue in https://gitlab.cern.ch/cms-cloud/cmssw-docker-opendata/-/issues/18#note_7141873)

The current MiniAOD mkedanlz instructions work in 7_6_7 container, so that correct.

[katilp]

Looks great! After a quick reading, the only point I have is to add a mention that the 2016 MiniAOD mkedanlz does not work as such.

[jmhogan]

Ok, @katilp do we not have the same "hack" in that container that we do in 767? If not, it would be useful to add it in the upcoming refreshes...

ETA: plan is to recheck all the commands today in 10-6h30, there was some issues with finding enough disk space for the container...

[katilp]

Ok, @katilp do we not have the same "hack" in that container that we do in 767? If not, it would be useful to add it in the upcoming refreshes...

This a different problem, it is not just to make it work: it works but provides a non-working example
So some heavier hacking would be needed. I'd go for a git repository with a basic equivalent skeleton

[jmhogan]

Ah, ok I remember now -- will check tonight and make a working EDAnalyzer in a repo And of course try to make the checks pass

…

On Wed, Jan 31, 2024, 10:15 AM Kati Lassila-Perini ***@***.***> wrote: Ok, @katilp <https://github.com/katilp> do we not have the same "hack" in that container that we do in 767? If not, it would be useful to add it in the upcoming refreshes... This a different problem, it is not just to make it work: it works but provides a non-working example So some heavier hacking would be needed. I'd go for a git repository with a basic equivalent skeleton — Reply to this email directly, view it on GitHub <#3551 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACVFOJCUPG3X26S5DBFLBF3YRJUY7AVCNFSM6AAAAABCSMV57KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJZGQZTKNJWGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[jmhogan]

@katilp new commits change up the EDAnalyzer example in MiniAOD:

• 2015 container pointed to mkedanlzr
• all others (2016 container, either VM) pointed to clone this: https://github.com/cms-opendata-analyses/MiniAnalyzer_CMSSW_10_6_30
  Tested in the 2016 container -- the analyzer itself is a direct copy of mkedanlzr in the 7_6_7 container. I haven't tested the VMs but would be surprised if it doesn't work as stated.

I also (for now) have removed the note that cmsenv should not be done in the container.

I need to triple check the rendering tomorrow on my desktop where I've worked up until now. I'm getting HTTPS Connection refused messages on my laptop when I run any of the instance cleaning or populating commands, though build, up, and down commands are successful.

To be seen whether I can pass the checks...

[jmhogan]

Ok, ready to go on my side.

[katilp]

Perfect, thanks!

[tiborsimko]

@jmhogan @Ari-mu-l Thanks, I'll rebase the branch and squash all the O(300) commits together into one and declare you both as co-authors. Hope that's OK? (CC @katilp)

[jmhogan]

Thanks @tiborsimko that sounds good -- it's too bad that the Github Preview is so helpful for markdown editing compared to rendering the site, very tempting to just hit that "commit" button. We discussed how to avoid so many commits in the future.

[tiborsimko]

Thanks @tiborsimko that sounds good -- it's too bad that the Github Preview is so helpful for markdown editing compared to rendering the site, very tempting to just hit that "commit" button. We discussed how to avoid so many commits in the future.

Thanks, I'll write over your PR then with everything squashed. BTW no problem in having many small commits whilst developing! It can be very useful. We are simply cleaning branches before merging as the last step, just to get rid of some intermediate commits when they aren't fully necessary to preserve. This facilitates future updates or bug fix hunting. (See also the developing guide.)

[tiborsimko]

Thanks, squashed as discussed, renamed the location of supporting images, added you and Xiaohe as co-authors.