• Created by Unknown User (mssgill), last modified on Feb 18, 2017

Date

Attendees

Goals

  • Prepare for review of the current single frame proc doc pages

Discussion items

ItemNotes
Current status of DMTN-030
  • Need to ask JimB for clarification on init'zn comments
  • Action item: JIRA tikt needs to be filed for someone (possibly JDS) to follow up with JimB on this
Current single-frame processing pages content
  • Pages are now in decent shape and waiting for an internal reviewer after some specific modifications
  • Changes needed:
    • All Tasks- Move: Command Line Arguments above config


    • In procCcd:
      • Raw is a ‘dataset type’ (not just a format), same for postisrccd
      • select between ordered and unordered list, don't combine

      • Make link at end to list of CLT args clear

      • Wording: sub-tasks → sub-task targets
    • In isrTask:
      • Refs at bottom can be useful
    • In calibImg:

      • Specify that afwdata needs to be set up for the example to work

      • Say that the PSF needs to be attached to the incoming data, not just determined


  • Action: make all the changes
  • Action: When ready MG will ask for a volunteer (JDS appears willing this time) to step up and do the review on the PR on branch DM-8717 - Getting issue details... STATUS of the sdp repo (https://github.com/lsst-dm/scipi_docs_prototype)


Longer term changes we want to aim at or discuss
  • Can we emphasize the params that get changed the most by putting them at the top of the list (and have a directive in the rst so autodoc picks it up separately) ?

  • Potentially we could show the key params that get changed most often, then have a button (implemented in javascript) that shows all the config flags




  • isrTask has so many options and does so much – perhaps it needs to be broken up eventually?


  • For the examples: can we do implement something like a simple web access to get the data for the examples vs. large git-lfs install requiring bringing in several Gb of sample data? [This may be superceded though with the obs_test pkg in place, which is only some 60M and is installed always as part of the Stack, now]


Action items

  •