User stories are a useful input to developing the concept for a software product and specifying the features. Typically, the stories have a lead off description of the form "As a (kind of user) I want to (do something) to (achieve something)." The elaboration of the user stories describe what inputs are needed, what outputs are expected, and what computations are performed.
Error rendering macro 'children'
Cannot invoke "com.atlassian.confluence.spaces.Space.getId()" because "space" is null
Candidate user stories
| Topic | Author | Comments |
|---|---|---|
Identify associated data sets | e.g. Find and download direct and dispersed images that overlap on the sky via an archive query | |
| Organization and bookkeeping | Conventions for file formats (in and out) metadata in files, file names, directory structure, output files (e.g. column names and units) | |
| Geometric transformations | Outline all of the variants and what the use cases are (e.g. elaborate from Nor's presentation) | |
| Astrometric registration | Align dithered observations | |
| Simulations | Create a simulated 2D dispersed spectrum from a 1D spectrum and image morphology | |
| Background subtraction | Russell Ryan | What are the different background components & approaches to estimating/subtracting for HST instruments? |
| Flatfielding | This can be subtle; the same approach can't be used in all circumstances. Maybe multiple user stories are needed? | |
| 2D spectral extraction | Maybe multiple stories with different approaches to getting a 2D extracted dispersed spectrum? | |
| Co-adding | Maybe several stories with different approaches to co-adding spectra taken at different orientations? | |
| Find an isolated emission line | Norbert Pirzkal | EM2D use case |
| Create an emission-line map | Create a 2D emission-line map from spectra taken at different orientations | |
| Fit a set of templates | Varying flux and redshift |
