Add some information about the template tier in the Rubin Scheduler to the Survey Strategy Website

Support
#1

I was trying to explain the template tier to some collaboration members, and I noticed there isn’t mention of it in the survey strategy website. It’s in PSTN-057 but for people not familiar with the cadence at all, I’m see that they’re struggling to understand that document and are doing better with the material in how it’s presented on the survey strategy website. Would it be possible to add a small section on the template tier?

1 Like
#2

Yes, I will add a small section on the template (or rather - the template acquisition strategy).
I’ll also add a note directing to other rubin_scheduler documentation on what “tiers” in the FBS configuration are.

1 Like
#3

Thanks @ljones - Slide 8 and Slide 12 from then SCOC-community workshop was a really helpful visual of what the tiers are and how they work . Maybe that could be posted too if it’s not in the rubin_scheduler documentation

1 Like
#4

heh, while I’ve got you as a tester …

We do have some general documentation in the Rubin-scheduler.lsst.io doc pages about how the FBS works.
Scheduler Overview — rubin_scheduler
However, because we don’t want to update that with every change in FBS configuration (and the FBS configuration itself is not part of rubin_scheduler, but rather a configuration repo elsewhere), it doesn’t describe the specific configuration we’re using for a particular simulation or at the summit.
Slide 8 would be reasonable to add to this documentation, but slide 12 would be too specific in my view.

What do you think? Is the overall documentation on that page at rubin-scheduler.lsst.io too technical and maybe we need another page describing general configuration of the FBS (where slide 8 could go)?
Or is this entirely just a different resource page (perhaps linked directly off the survey-strategy.lsst.io website, maybe just containing the tier + survey highest level info)?

1 Like
#5

What’s on rubin-scheduler.lsst.io is way too technical for the average data right holder. It’s super useful information to have (it looks great). I’d say links to more detailed documentation with general overview descriptions is good. Which I think the survey strategy page does really well for the it has content.

1 Like
#6

I have made a JIRA ticket for this work as clarified here, and will mark this as the solution.

1 Like
#7

Thank you.

1 Like