You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Inter-Team (Within DM) Discussion Requests

Requestor(s)ParticipantsTopic
   

 

Other Sessions

Session Description and GoalPlenary or Required ParticipantsLengthRequester
Authentication and Authorization: convey what is feasible technically, what policy implications that has, and state of current prototypePlenary??James Basney
OCS Middleware: further refine ICDs"Principal System Software Interactions" Group4 hr?Gregory Dubois-Felsmann
Engineering and Facilities Database: define responsibilities and technical details of replication of "verbatim" copies of EFDDave Mills1 hr?Donald Petravick
Visualization: work with Camera team on improving current visualization systemUnknown User (jjt)2 hr?Unknown User (xiuqin)
Wavefront estimation: The T&S group have developed a wavefront estimation code which we plan to incorporate into the DM stack as part of 02C.04.03 (PSF estimation). Discuss its current state, what work remains to be done, and how best to proceed with integration.Sandrine Thomas, Unknown User (schandra)2 hr?John Swinbank
End to End Computing Support for Observing: walk though of capabilities/expectations on 1) "quick look" capabilities provides by the T&S project, 2) uses of the commissioning cluster, and 3) L1 processing system.TBD S&T people, someone to represent observing staff2hr?Donald Petravick
Networks: Review current contracts and schedules, recent LSE-78 updates, Network Operations and Management Plan, Network End-to-End Test plan.

Paul Wefel

Unknown User (rlambert)

Chip Cox (only available after 11am on 2/24)

Other FIU people remotely (need videocon support)  Julio Ibarra, Jeronimo Bezerra , and Heidi Morgan

Optionally Camera people who are in town for JTM (Mike Huffer, Tony Johnson),

3 hrJeff Kantor
Virtual Observatory: Talk about current strategies and whether we should take a more focused approach on standards involvement for Summer16.John Swinbank, Unknown User (ciardi), Mario Juric, Jacek Becla plus anyone else interested2 hrTim Jenness
Unicode: I would like to re-assess the lack of requirement for using Unicode in LSST. In the 2020s (and now) unicode is an accepted part of life and it seems strange that we will be unable to include names and math symbols in observing logs and processing logs.OCS representative, SQuaRE representative, John Swinbank, Jacek Becla2 hrTim Jenness

Python3 Migration: I would like to start planning the python3 migration of the DM software so it can be integrated into the Summer16 development plan.

John Swinbank, Simon Krughoff, Jonathan Sick2 hrTim Jenness

Documentation & Technical Communication Tools Spearheaded by DM. This session will review the new doc and web publishing work by DM, with the goals of: seeking adoption by other groups, coordinating with the project communications, and setting goals for Summer16 development. Topics will be:

  1. community.lsst.org - review status of the forum and the Mailbot service to integrate the forum with our existing mailing lists. Can more groups use the forum?
  2. Technical Notes - We've launched a new Technical Note platform to distribute web-native reports that capture information not applicable to change-controlled docs in Docushare or academic papers, while also being citeable in the astronomical literature (unlike Confluence pages or Docushare docs). I'll demonstrate the platform (Sphinx, GitHub, readthedocs.org, Zenodo), and how records are being listed in NASA/SAO ADS.
  3. docs.lsst.io - I'll talk about the new documentation landing page we're crafting to make all of DM's artifacts discoverable (software documentation, developer guides, technical notes, design documents, science papers, conference posters/talks/videos). The site will be automatically built from data in repositories such as Zenodo and ADS, and will integrate with the LSST DM bibliography being curated by Tim Jenness.
  4. Sphinx-based software documentation. I'll review the status of DM's new Sphinx-based documentation tooling to publish a new Developer Guide and docs for Science Pipelines, Qserv and Firefly. We're building a clone of ReadTheDocs.org to continuously deploy docs from our Eups/Scons-based software projects. I'd like to have an open discussion of what our priorities for software documentation should be in Summer16.
Anyone in other groups working on technical communications and software documentation. Members of DM are especially invited to give feedback on S16 planning. Of potential interest to: Beth Willman, Unknown User (suzanne), Zeljko Ivezic, Unknown User (schandra), Peter Joachim1+ hrJonathan Sick
Naming: This may sound like a tongue in cheek request, but it would be good if we could spend a bit of time trying to come up with a name for the software that DM is writing. We have Qserv, Firefly, SUIT but we don't have anything for the science pipelines. This makes it hard to develop branding.Anybody who would have an opinion.0.5 hrTim Jenness
  • No labels