udaykiran19491/user-stories-from-tawos-for-llm-fine-tuning huggingface dataset:
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The flex fixes manually applied in DM-4728 are now part of an official doxygen release. This ticket concerns updating the LSST doxygen to that version (1.8.11) and testing the builds.    Doxygen is tagged "u" on the DM Third party packages page on confluence so an RFC is not required before initiating an upgrade.
Answer: 872546.0

User story: "The git-lfs client (1.1.0+) does not support empty username and passwords. To work around this, users can store the appropriate credentials directly with the credential helper."
Answer: 8537.0

User story: "Some of the operations we currently run as part of measurement (or would like to) share some features that make them a bit different from most plugin algorithms:   - They must be run after at least some other high-level plugins, and may be run after all of them.   - They do not require access to pixel data, as they derive their outputs entirely from other plugins' catalog outputs.   - They may require an aggregation stage of some sort to be run on the regular plugin output before they can be run.    Some examples include:   - Star/Galaxy classification (with training done after measurement and before classification).   - Applying aperture corrections (estimating the correction must be done first).   - BFD's P, Q, R statistics (requires a prior estimated from deep data).    We should move these algorithms to a new plugin system that's run by a new subtask, allowing these plugins to be run entirely separately from {{SingleFrameMeasurementTask}}.  This will simplify some of the currently contorted logic required to make S/G classification happen after aperture correction, while making room for hierarchical inference algorithms like BFD and Bayesian S/G classification in the future.    (We will not be able to support BFD immediately, as this will also require changes to our parallelization approach, but this will be a step in the right direction).    This work should *probably* be delayed until after the HSC merge and [~<USER>'s rewrite of {{ProcessCcdTask}} are complete, but it's conceivable that this refactoring could solve emergent problems there and be worth doing earlier as a result."
Answer: 138278.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The ability to automate the launch of htcondor pools of worker nodes  (e.g., with LSST software installed) on the Nebula OpenStack can be useful  in several ways for LSST DM.  On one hand, users can start up their own customized  pool should the standard pool available on other resources such as lsst-dev not  be suitable (e.g., not enough cores, not enough memory per core/slot,  customized software not installed on the systems, etc.)  Also, scripted launch  of a pool can be part of the development of a solution for offering  "batch" scheduling to the Nebula OpenStack, following an approach similar to e.g.,  CANFAR ( http://www.canfar.net/docs/batch/ , http://cloudscheduler.org)  whereby  a "cloud scheduler" is used in conjunction with an htcondor central manager  to provide batch access to the cloud (i.e., submitted jobs are placed into an htcondor queue,  that will execute on launched instances, when those instances join the working pool.)  
Answer: 21665.0

User story: The idea is that our current integration test is using "mono" configuration which is only useful for integration test but it's not used anywhere else. It would be more useful to have an integration test which is close to real setup, e.g. used more than one worker. It should still be possible to run the whole shebang on a single node though to keep it usable for regular development tasks.
Answer: 939538.0

User story: "Since DM-4235 was merged, we see a bunch of messages along the lines of:  {code}  processCcd.measurement WARNING: Error in base_Variance.measure on record 427969358631797076: The center is outside the Footprint of the source record  {code}  in the output from {{lsst_dm_stack_demo}}. (See e.g. [here|https://ci.lsst.codes/job/stack-os-matrix/label=centos-6/7482/console#console-section-3]). It's not fatal, but the warnings are disconcerting and could be indicative of a deeper problem."
Answer: 9538.0

User story: "If the image and mask don't have the same size, we can get a NAN result if all pixels in the lower-left are masked. This patch add a check on the size of all images to catch accidental user errors.    This is a (partial) port of work performed on [HSC-1290|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1290] (for the HSC-1290 changes to {{meas_extensions_shapeHSM}}, see DM-3384)."
Answer: 3923.0

User story: "We are testing the bokeh library plot for interactive visualization in the web, the python API is atractive and allows rapid prototype which is good for SQuaRE build up its QA system.    Some examples are available in this repo, including a scatter plot with linked histograms in both axis which seems really useful.    https://github.com/lsst-sqre/bokeh-plots    A more complete demonstration of bokeh is available in this webminar:     https://continuum-analytics.wistia.com/medias/f6wp9dam91    And more recently here https://github.com/pzwang/bokeh-dashboard-webinar    "
Answer: 72103.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It's convenient if we can assume that coadd input catalogs are contiguous -- it simplifies the implementation of {{PropagateVisitFlagsTask}} (DM-4878), for example. Make it so.    This is port of work carried out on [HSC-1293|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1293]."
Answer: 23017.0

User story: It is useful to be able to identify suitable PSF stars from a coadd catalogue. However, the PSF is not determined on the coadd, but from all the inputs. Add a mechanism for propagating flags from the input catalogues to the coadd catalogue indicating stars that were used for measuring the PSF.    Make the inclusion fraction threshold configurable so we can tweak it (so we only get stars that were consistently used for the PSF model; the threshold might be set it to 0 for "or", 1 for "all" and something in between for "some").    Make the task sufficiently general that it can be used for propagating arbitrary flags.    This is a port of work carried out on [HSC-1052|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1052] and (part of) [HSC-1293|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1293].
Answer: 20263.0

User story: "Diagnostic plot showing the number of process ccd failures in each visit as function of the density of sources.    - Use the butler to iterate over the data ids, read the src catalog and count the number of sources per ccd.    - Use afw.display.ds9 to display the image and overlay the sources"
Answer: 3.0

User story: "Compile list of DM simulation needs over the next ~6 months to give to Andy Connolly (simulations lead)."
Answer: 3.0

User story: "The matchOptimisticB matcher fails on many visits of the bulge verification dataset.  This prompted a deeper investigation of the performance of the matcher.  Angelo and David developed a test script and discovered that the matcher works well with offsets of the two source catalogs of up to 80 arcsec, but fails beyond that.  This should be robust enough for nearly all datasets that the LSST stack will be used on."
Answer: 1.0

User story: "Start from example provided by the firefly team    https://github.com/lsst/suit"
Answer: 5.0

User story: "The DECam bulge survey is being processed as part of the verification data sets effort. During astrometry calibration task a large number of failures (affecting ~100 of 213 visits) have been found in calibrate.astrometry.matcher. We report here details of the investigation around this issue. Part of the task is to learn how to use the task built in debug.     More info:    https://confluence.lsstcorp.org/display/SQRE/Bulge+Survey+Processing#BulgeSurveyProcessing-Results"
Answer: 81065.0

User story: "Follow instructions at   https://confluence.lsstcorp.org/display/DM/1.+Quick+Start+-+LSST+Cluster+Orchestration    to set up the required packages to run the lsst stack at lsst cluster."
Answer: 5.0

User story: "Install Astrometry.net Index Files for 2MASS all sky catalog"
Answer: 3.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Created a script to setup required LSST stack packages for bulge survey processing.  "
Answer: 14.0

User story: "HSC has its own implementation of background matching: see {{background.py}} in {{hscPipe}}. Please port it to the LSST stack."
Answer: 1067.0

User story: "This story involves setting up a webserv in a VM (NCSA OpenStack) with a small data set: images and corresponding database catalog. We need to   * setup VM   * build the stack for webserv and qserv   * identify images to load   * run qserv in the VM   * run ingest to load the data to mysql (mysql will run on lsst10) and qserv (qserv will run directly in the VM)   * run two webservers - one with mysql backend, one with qserv backend   * open the port numbers for the IPAC team"
Answer: 1520496.0

User story: click and highlight a point.  Is on when mouse readout "Lock by Click" is on. However, can me turned on externally by adding toolbar context menu options.
Answer: 63773.0

User story: "With the current master and default config, astrometry fails when processing raw data of south CCDs. Warning message:   {code:java}  processCcd.calibrate WARNING: Unable to perform astrometry (Unable to match sources): attempting to proceed  processCcd.calibrate WARNING: Failed to determine photometric zero-point: No matches available  {code}      Matching fails because the wcs of the input {{postISRCCD}} exposures are shifted by a large amount.  {{processCcd.py}} astrometry can run successfully with the config {{calibrate.astrometry.matcher.maxOffsetPix=1400}}.     This plot !patchesCmp35a.png|thumbnail! shows the wcs of 2 neighboring CCDs, N4 (35) and S4 (28), by drawing the ra/dec boxes from {{raw}} (black), {{postISRCCD}} (blue), and {{calexp}} (red).      The shift appears because the first amplifier in a detector is assumed to be the amplifier at the lower left corner. The assumption is not true for all south chips of the current DECam camera geometry setup, and hence introduces a large shift in the wcs of the postISRCCD products.       One way to fix this is to modify the amplifier segments file {{obs_decam/decam/segmentfile.txt}} and ensure the lower-left amplifier is the first amplifier of a detector.  With the changes in {{obs_decam}} of this ticket, {{processCcd.py}} can run with the default config (including those in master obs_decam/config/processCcd.py and  isr.assembleCcd.setGain=False DM-4232). The same wcs plot becomes !patchesCmp35b.png|thumbnail!      Note that the {{raw}} image (black) include prescan/overscan regions. {{postISRCCD}} (blue) is trimmed. Otherwise they share the same ra/dec boxes as they should. !illustration-sky.png|thumbnail! is an illustration of the two CCDs in sky orientation (not to scale)."
Answer: 24022.0

User story: "It's confusing to have to use an extra {{[:]}} to set a column in afw.table, and we can make that unnecessary if we override {{\_\_setitem\_\_}} as well as {{\_\_getitem\_\_}}."
Answer: 14511.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This ticket incorporates work to be done in [DM-3368|https://jira.lsstcorp.org/browse/DM-3368], [DM-3369|https://jira.lsstcorp.org/browse/DM-3369], and [DM-3370|https://jira.lsstcorp.org/browse/DM-3370]. Much of the work may depend on each other, and testing will be made much easier if the work for each of these tickets could share a common branch. This will avoid a situation where a given package may need to be set up on two different ticket branches simultaneously. "
Answer: 70440.0

User story: "The current astrometry_net_data package in github does not actually provide any data. It is a placeholder so that any packages which depend on it won't fail on setup. However, any attempted usage of the package will fail, and it is unclear to the user why this (intentional) failure is occurring.    This ticket will 1) add a README to the package to explain that it is a placeholder and 2) add an andConfig.py file that will print an error message to the user if they attempt to use it for astrometry.  "
Answer: 243908.0

User story: "Write action and reducers for XY Plot"
Answer: 11930.0

User story: "{{MeasureMergedCoaddSourcesTask.setIsPrimaryFlag()}} and {{ProcessCoaddTask.setIsPrimaryFlag()}} are effectively the same code. Please split this out into a separate task which both of the above can call.    This is a (partial) port of [HSC-1112|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1112] and should include fixes from [HSC-1297|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1297]."
Answer: 29277.0

User story: "1. Calculate and plot photometric variability across series of N images.  Compare to reported photometric errors.  Designed for N > 5.  2. Calculate and plot Delta flux / sigma_flux for multiple observations of stars in field.  This is related to 1. but is focused on N=2 to N=5.  3. Fit uncertainty distribution vs. magnitude to identify any floor in the photometric uncertainty and to check performance vs. photon counts."
Answer: 31261.0

User story: "[HSC-1316|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1316] shifts the calculation of blendedness from {{meas_deblender}} to {{meas_algorithms}} and defines a new blendedness metric in the process. Please port it."
Answer: 51463.0

User story: "{{MeasureMergedCoaddSourcesTask}} needs an astrometry task to match sources, but it does not need to derive a new astrometric solution. Indeed, doing so is not merely wasteful, but incorrect: the derived solution is not persisted, but source positions calculated based on it are, and cannot therefore be reproduced    This is a port of [HSC-1318|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1318]."
Answer: 41611.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In DM-2914 (specifically, in [73ed9bc8|https://github.com/lsst/meas_deblender/commit/73ed9bc816a3fd5613b8c5c2e0eb1ce77b22bb7e]) a change was made to the calculation of variance.    This is incorrect: while deblending does split up the noise part of the pixel values as it splits up the signal, we don't want to account for that in the variance plane, because we're even more uncertain about value of deblended pixels than we are unblended pixels. Please revert it.    This is a port of [HSC-1334|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1334]."
Answer: 952.0

User story: "Propagating flags requires matching against CCD visit catalogues or astrometry.net, which is inconvenient if the relevant data files aren't available. Please make it optional.    This is a port of functionality implemented on [HSC-1343|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1343]; see also DM-4843 for other work on that ticket."
Answer: 45917.0

User story: "{{MeasureMergedCoaddSourcesTask}} only uses an astrometry subtask if {{doWriteMatches}} is {{True}}. Please don't initialize it unless it's required.    This work was originally part of [HSC-1343|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1343]."
Answer: 44404.0

User story: "There's no need to persist {{HeavyFootprint}}s while performing forced photometry since retrieving them is as simple as loading the _meas catalog.    This is a port of [HSC-1345|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1345]."
Answer: 44328.0

User story: "We are currently choosing the priority band as the reference band for forced photometry as long as it has a peak in the priority band regardless of the S/N.  Please change this to pick the highest S/N band as the reference band when the priority band S/N is sufficiently low.    This is a port of [HSC-1349|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1349]."
Answer: 81974.0

User story: Please add "sources" corresponding to empty sky (ie, at positions where nothing else has been detected) and include them in multiband processing.    This is a port of [HSC-1336|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1336] and [HSC-1358|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1358]. 
Answer: 50198.0

User story: "Create high-level overview of Data Release Production, probably as an annotated flowchart, for use in sizing model work and as a graphical table of contents for more detailed descriptions."
Answer: 74682.0

User story: "Per DM-3766, [~<USER> spotted a problem in the way that {{obs_subaru}}'s {{genCalibRegistry.py}} adjusts {{validStart}} and {{validEnd}} to avoid conflicts. This has been fixed in {{pipe_tasks}}'s {{ingestCalibs.py}}, but is still an issue with {{obs_subaru}}'s {{genCalibRegistry.py}}.    It's not clear if the latter is actually still relevant (DM-4740); on the assumption it is, the fix from [HSC-1362|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1362] should be applied."
Answer: 80519.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Please port the prototype Brighter-Fatter correction work by Will Coulton from HSC.    This covers [HSC-1189|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1189], [HSC-1332| https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1368], [HSC-1368|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1368]. Note also the stand alone commits [783b124|https://github.com/HyperSuprime-Cam/obs_subaru/commit/783b124b6813f5745ce1e444f61fb0114d055907] and (if this work is performed after DM-3373) [9fc5e78| https://github.com/HyperSuprime-Cam/obs_subaru/commit/9fc5e78247e7173e095255dba34e994f73a6bd1d]."
Answer: 32930.0

User story: "On some systems, we are asked to request a total number of tasks, rather than specify a combination of nodes and processors per node.    It also makes sense to use the SMP option this way.    This is a port of [HSC-1369|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1369]."
Answer: 23210.0

User story: "This is the equivalent of DM-3942 but through coadd processing.    Relevant HSC tickets include:    * [HSC-1371|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1371]"
Answer: 144060.0

User story: "The {{obs_subaru}} configuration for Suprime-Cam needs updating to match recent changes in the stack.    Port of [HSC-1372|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1372]."
Answer: 63352.0

User story: "Add filter definitions and colour terms for the new HSC filter.    This is a port of [HSC-1374|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1374]."
Answer: 44743.0

User story: "Given per-patch inputs providing   {code}  id, B, V, R, ra, dec, radius    {code}  for each star to be masked, use this information to set:  * A bit in the mask plane for each affected pixel  * A flag in the source catalogues for each object that has a centroid lying within this mask area    This is a port of [HSC-1342|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1342] and [HSC-1381|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1381]."
Answer: 82447.0

User story: "The {{ShapeletPsfApprox}} Task uses a class called {{PsfFitter}} which is not a {{SimpleAlgorithm}} and does not support error handling.  Add error handling to this class, and modify the Task definition in {{psf.py}} to call an {{errorHandler fail()}} function when the algorithm's {{optimizer.run()}} call fails.    Also, add unit tests"
Answer: 20070.0

User story: "Move Python files into python/lsst namespace convention.  Decide on where {{validateCfht.py}} and {{validateDecam.py}} executables should live  Add package requirements to {{ups/validate_drp.table}}"
Answer: 13072.0

User story: "Try to understand, without doing actual implementation what is involved in  implementation of support for asynchronous queries in Qserv and possibly web interface. Should result in a roadmap for implementation at all levels.  "
Answer: 65604.0

User story: "FitsDownload dialogs html and css is not quite right. Needs some clean up."
Answer: 15447.0

User story: "Add the dropdown to the vis tool bar"
Answer: 5422.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "DM-4133, DM-4800, DM-4709, DM-4707, DM-4814"
Answer: 23905.0

User story: "This is a port of [HSC-1353|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1353] and [HSC-1360|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1360].    Descriptions from HSC:   {panel:title=HSC-1353}  We typically get a large number of junk detections around bright objects due to noise fluctuations in the elevated background. We can try to reduce the number of junk detections by adding an additional local background subtraction before object detection. We can then add this back in after detection of footprints and peaks.  {panel}  {panel:title=HSC-1360}  I forgot to set the useApprox=True for the background subtraction that runs before footprint and peak detection. This will then use the Chebyshev instead of the spline.  {panel}"
Answer: 15800.0

User story: "Read through and run the `ci_hsc` tests and plan for how this module and efforts should relate to `validate_drp`.    a. Add capabilities to `validate_drp` to run the tests in `ci_hsc`.  (/)  b. Compare frameworks. (/)  c. Plan for how such validation and continuous integration data sets should be constructed. (/)  "
Answer: 64979.0

User story: "Write initial draft of [SQR-006|http://sqr-006.lsst.io] that specifies how the documentation deployment service will work."
Answer: 20888.0

User story: "Create a `validation_data_decam` to provide a few images for DECam validation tests.    Use the COSMOS field data as currently available on NCSA being processed by [~<USER>.    Select just a few images for now."
Answer: 12471.0

User story: "There are some very low level modules that depend on mysqlclient (for example daf_persistence). It'd be too harsh to make them depend on mariadb, so we should package mariadb client."
Answer: 10818.0

User story: "Some information should be added to CSS to indicate if a table should be locked in memory for shared scans and the effect the table is likely to have on the time it takes to complete a query."
Answer: 12184.0

User story: "Now that we switched Qserv to mariadb, it'd be good to switch the rest of the stack. This story involves trying out if things still work if we switch mysqlclient to mariadbclient."
Answer: 27256.0

User story: "Header keys such as PVi_j left in the raw metadata confuse the making of wcs in later processing steps.   For example, when {{calexp}} is read in {{makeDiscreteSkyMap.py}}, {{makeCoaddTempExp.py}}, and so on, this message appears:  {code:java}  makeWcs: Interpreting RA---TAN-SIP/DEC--TAN-SIP + PVi_j as TPV  makeWcs WARNING: Stripping PVi_j keys from projection RA---TPV-SIP/DEC--TPV-SIP  {code}  These {{calexp}} are created by running {{processCcd.py}} on raw data, and are mis-interpreted as TPV.  "
Answer: 11443.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In DM-4410 default configuration options were changed such that footprints are now grown in the detection task, and the deblender is run by default. This breaks the lsst_dm_demo, as now the results of processing are slightly different. The short term solution as part of DM-4410 was to run the demo with the defaults overridden to be what they were prior to DM-4410. In the long term the values used in the compare script should be updated to reflect what would be generated with running processCcd with the stack defaults. "
Answer: 168165.0

User story: "Our current method of converting a {{Mask}} to a {{FootprintSet}} is memory intensive. A more efficient version is available on [HSC-1231|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1231]."
Answer: 1096.0

User story: "DetectCoaddSourcesTask.scaleVariance is used to adjust the variance plane in the coadd to match the observed variance in the image plane (necessary after warping because we've lost variance into covariance). The current implementation produces the wrong scaling in cases where the image has strongly variable variance (e.g., 10 inputs contributed to half the image, but only 1 input contributed to the other half) because it calculates the variance of the image and the mean of the variance separately so that clipping can affect different pixels.    Getting this scaling very wrong can make us dig into the dirt when detecting objects, with drastic implications for the resultant catalog.    This is a port of [HSC-1357|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1357] and [HSC-1383|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1383]."
Answer: 7227.0

User story: "{{assembleCoadd.py}} in {{pipe_tasks}}  {code:python}  637 class SafeClipAssembleCoaddConfig(AssembleCoaddConfig):  [...]  670     def setDefaults(self):  671         # The numeric values for these configuration parameters were empirically determined, future work  672         # may further refine them.  673         pexConfig.Config.setDefaults(self)  674         self.clipDetection.reEstimateBackground = False  {code}    Line 673 should call to the superclass's {{setDefaults()}} method; instead, it is bypassed and we jump straight to {{pexConfig.Config.setDefaults()}}."
Answer: 57.0

User story: The ISR task configuration should enable the user to specify a "fallback" filter which will be used when calibrations for a particular filter aren't available.    This is a port of work performed on [HSC-987|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-987].
Answer: 80968.0

User story: "A {{CameraMapper}} subclass should be able to specify a default filter name to be used when the filter is not found in {{self.filters}}. This will allow processing images with filter names that have not been previously anticipated, as might be desired for onsite analysis.    This is a port of work performed on [HSC-987|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-987]."
Answer: 83705.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Write the simple zoom options popup that is show when the user clicks zoom too fast or the zoom level exceeds  the maximum size.      activate this popup from visualize/ui/ZoomButton.jsx"
Answer: 113732.0

User story: "Refactor [lsst_stack_docs|https://github.com/lsst-sqre/lsst_stack_docs] into two doc projects    - LSST DM Developer Guide that will be published to {{developer.lsst.io}}, and  - LSST Science Pipelines that will be published to {{pipelines.lsst.io}}"
Answer: 11100.0

User story: "add toggle button that make the mouse readout lock to last position click on.  It will not longer update on move but by click  Include: 3 Color Support"
Answer: 102560.0

User story: "Call the server when mouse pauses, include the flux value in the readout. The should also include support for 3 color."
Answer: 73933.0

User story: "See https://mariadb.atlassian.net/browse/MDEV-9389"
Answer: 670.0

User story: "Current provenance schema in baseline (cat/sql) is very old and no longer reflect latest thinking. This story involves bringing cat/sql up to data and replacing existing prv_* tables with tables we came up with in the epic."
Answer: 22808.0

User story: "The LSST Publication Board requests a JIRA project for managing its workload.       "
Answer: 95188.0

User story: "* Setup IPMI on lsst-esxi3, lsst-esxi5, lsst-esxi6  ** Created ipmitools binary - Ubuntu 12.04 has the correct libraries for ESXi6  ** Installed on lsst-esxi3, lsst-esxi5, lsst-esxi6  ** Configuration worked well on lsst-esxi5, lsst-esxi6.  ** lsst-esxi3 is actually lsst-esxi4.  System will not respond to ipmitool commands - suggest waiting for scheduled outage and manually setting up ipmi.  * Debugged networking issues with new equipment  * Cleanup of crashplan archives for new lsst system  * Mac VMs  ** Working on figuring out Mac VM requirements and process with Josh Hobblitt  ** Attempted to install and configure puppet on Mac VMs - running into configuration issues  "
Answer: 1.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending December 12, 2015."
Answer: 2.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending December 5, 2015."
Answer: 3.0

User story: "Three significant changes were made to CModel in [HSC-1339|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1339]. They were described by [~<USER> in a [post to {{hsc_software}}|http://jeeves.astro.princeton.edu/pipermail/hsc_software/all/4568.html]. They include:    * Changing the method by which the initial approximation is determined;  * Changing the determination of the pixel region to use in fitting;  * A new prior on ellipticity and radius.    Please port these changes to LSST.    Also include the results of fixing the bug described in [HSC-1384|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1384]."
Answer: 88977.0

User story: "Evaluated first cut of CONOPS document. Formulated queries for clarifying specific questions regarding ldm-230 - 2"
Answer: 14.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Begin evaluation of potential in-memory data storage tools - selecting memcached and redis to start. - 4    With the intent  to gain familiarity with these tools, procurred introductory volume on redis and began writing prototype python code to prototype lists, hashes, and lists of hashes. Sketched out and implemented base python class with virtual save method, then wrote child classes for replicators, replicator health, replicator jobs etc. and tested this code and implemented the save methods. - 4    Installed the above code on a nebula instance that acts as a job manager, then ran real job messages through the system and simulated task assignment and completion, using redis to track jobs. - 2    Exploring how a logging and visualization harness might be included so job activity could 1) be observed in realtime, and 2) so a session could be played back as an after action review to investigate errors, bottlenecks, cold restart behavior, etc. - 2    To finish out this story, redis replication must be included in the above prototype."
Answer: 110884.0

User story: "defines various image data types, how to get them, groupings, artifacts.   I am not quite happy with how we did in in GWT so the design needs to be improved.  Must be less complex."
Answer: 141361.0

User story: "* port of MultiDataView.java  * support grids, rows, finger chart type grid  * support paging with table data sets  * support DatasetInfoConverter port  * The components should be able to display any group of data  * Critical for Firefly Viewer"
Answer: 102647.0

User story: "Per discussion 1/6/2016, it'd be nice to have a function that generates user-friendly threadId  on Linux to simplify debugging."
Answer: 72427.0

User story: We need access to database schema for various reasons (analyzing queries, checking authorization, for queries like "show create table" and others).
Answer: 13296.0

User story: "we place anonymous namespace in two ways: (a), INSIDE lsst::qserv::<module> namespace, or (b) BEFORE. This story involves cleaning it up - move them to before lsst::qserv::<module>"
Answer: 5947.0

User story: Builds on MacOS 10.11 have been painfully slow (for instance 23 minutes to build {{afw}} instead of the more typical 12 minutes, 30 minutes to rebuild {{ip_diffim}}, 20 minutes to rebuild {{meas_astrom}}) and much of this time is spent running fc-list in 8 cores.    I suspect {{matplotlib}} is triggering this process, but I have not verified it.    I see this using lsstsw to build a fresh stack and with manual builds.    A workaround is to repeatedly kill {{fc-list}}, e.g. with this bash script:  {code}  while sleep 1; do pkill fc-list; done  {code}    I checked my fonts with Apple's Font Book and found a few dozen with "minor errors" that I deleted, but nothing serious. I'm still seeing the problem.
Answer: 2365893.0

User story: "Create a demo, which takes a URL and shows a table with a histogram viewer connected to it."
Answer: 7179.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Read Gartner materials related to ITIL, devops  IT organization in preparation for more detailed thinking about Data Operations.    One major category of thought is "Mode 1 and Mode 2" type organizations. Mode ! is the current typical controlled environment the strength is when something precious needs to be managed.  For LSST this might be the data release production, which is baselined to be 9 months on a unique resource that the project procured.  Mode 2 is "doves" which is best used for nimble, fall fast software.  An example e testing algorithms.
Answer: 1.0

User story: "self explanatory"
Answer: 11.0

User story: "Prepared two longer con accompanied by (hand drawn activity diagrams).      One conops /activity  diagram describe the work at the archive center to provide and support the L1 services used by telescope operations.    the second activity diagram and conops respdes to Chuck Clavers' request to have materials that explain the relationship of the stiletto computing center at CCIN2P3 to Archive Center at NCSA.    Both are DRAFT; and coops seem to be systems engineering documents, and where to deliver a blessed version and who is responsible for this is unclear to me. "
Answer: 16.0

User story: "One foundational document  required for how NCSA Astronomy Core Services working methods that is missing is a concept of operations (CONOPS) for the L1 system.     Better late than never,  I wrote a L1 cops illustrating the uses of the L1 system, allowing for further specifications and context for all staff involved in the project. the document currently exists a a draft in google docs.  It's been review by Mario and KT.  This is more properly a systems engineering document, not at all sure where a final home for it belongs (or how it acquires status)"
Answer: 29.0

User story: "Configure mod_auth_oidc on lsst-auth1 with CILogon and Globus."
Answer: 38798.0

User story: "Bi-weekly IaM meeting between NCSA and LSST for the month of December 2015.  Local coordinating meetings also included."
Answer: 1.0

User story: The "Kernel Panic" issue is non-blocking right-now for John due to machine automated reboot, but we have to solve it to target a stable production system.    With Yvan, we're converging on next update for the cluster:    - on my side I update Qserv metadata on ccqserv100 w.r.t. new Qserv metadata format, and then I test Docker+Qserv on ccqserv100->ccqserv124,  - then CC-IN2P3 team launches a upgrade of the kernel to kernel-ml ( "mainline stable" branch of The Linux Kernel Archives) on ccqserv100->ccqserv124, this could be done in January,  - I control Qserv behaviour is still the same than before,  - then Qserv developpers can use this cluster to see if "Kernel Panic' issue is solved.    If it work we'll update to kernel-ml on ccqserv125->ccqserv149, if it doesn't, cc-in2p3 and Qserv developpers will have to find an other solution.    Regards,    Fabrice
Answer: 164825.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Option "mysql_options( m, MYSQL_OPT_LOCAL_INFILE, 0 );" is added to all C++ sql client instance due to common sql interface, but is only required on master (for merging results) is it possible:   - to remove LOCAL keyword (on czar virtfile is on the same machine that mariadb server)  - or to set it in Qserv czar/master configuration  - or to set it in master MariaDB instance only?
Answer: 1778184.0

User story: "mysqlproxy is not compliant with mariaDB client: see https://mariadb.com/kb/en/mariadb/mariadb-vs-mysql-compatibility/#incompatibilities-between-mariadb-and-mysql-proxy    Nevertheless the trivial fix proposed (remove progress-report options) doesn't seems to work...  {code:bash}    mysql --host=127.0.0.1 --port=4040 --user=qsmaster --batch qservTest_case01_qserv    ERROR 1043 (08S01): Bad handshake  {code}"
Answer: 10195.0

User story: " - remove scratch db?  - cleanup tmp/sql/*.sql filesi  - remove xrootd configuration script if useless?   - cleanup configuration script style (i.e. tmp/*.sh)  "
Answer: 2200522.0

User story: The afw package does not build reliably (if at all) on a linux box at UW ("magneto", which has 32 cores and 128 Gb of RAM). The failure is that some unit tests fail with the following error:  {code}      OpenBLAS: pthread_creat error in blas_thread_init function. Error code:11  {code}    For the record, /usr/include/bits/local_lim.h contains this:  {code}  /* The number of threads per process.  */  #define _POSIX_THREAD_THREADS_MAX 64  /* We have no predefined limit on the number of threads.  */  #undef PTHREAD_THREADS_MAX  {code}    It appears that the build system is trying to use too many threads when building afw, which presumably means it is trying to use too many cores. According to [~<USER> the package responsible for this is {{eupspkg}}, and it tries to use all available cores.    A workaround suggested by [~<USER> is to set environment variable {{EUPSPKG_NJOBS}} to the max number of cores wanted. However, I suggest we fix our build system so that setting this variable is unnecessary. I suggest we hard-code an upper limit for now, though fancier logic is certainly possible.    A related request is to document the environment variables that control our build system. I searched for {{NJOBS}} on confluence and found nothing.
Answer: 59154.0

User story: "A repository which does not use Git LFS is created and described in {{repos.yaml}}. It runs through CI, and is cloned onto a Jenkins build slave. Subsequently, the repository configuration in {{repos.yaml}} is updated to enable LFS. The build system should notice this change and update the cloned repository on disk appropriately. Currently, it doesn't."
Answer: 1647959.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The contract for `daf.butlerUtils.CameraMapping.parentSearch` states that `None` will be returned if no matches are found.    But in one of the options  `            if os.path.realpath(pathPrefix) != os.path.realpath(root):`  the code says `return []` instead of `return None`.    This is then not caught properly by `daf.butlerUtils.mapping.map`, which was checking just for the return value `is not None`.      The behavior of parentSearch is clearly an error (it's againt the documentation for the function).    I would also suggest that `daf.butlerUtils.mapping.map` should check more robustly for `if newPath:` rather than `if newPath is not None:`.    Thus we explicitly set up this if/else to return `None` if `not paths` instead of `[]`.    "
Answer: 29687.0

User story: "The plots output by the qa analysis script (see DM-4393) currently do not display any information regarding the selection/rejection criteria used in making the figures and computing the basic statistics.  This includes magnitude and clipping thresholds.  This information should be added to each plot such that the figures can be interpreted properly."
Answer: 113315.0

User story: "The qa analysis script ported from HSC and adapted to LSST on DM-4393 currently performs qa on single visit processing by comparing outputs of a single run from the different measurement algorithms and comparing those with the astrometry/photemetry reference catalog.  Here we will add functionality to directly compare two different runs of the same dataset (requiring accommodations for two butlers).  Since the goal is to compare outputs from runs on the LSST vs. HSC stacks, this will require a mapping of the different schemas of the persisted source catalogs of the two stacks."
Answer: 53519.0

User story: The qa analysis script under development (see DM-4393) calls to HSC {{hscPipeBase}}'s [matches.py|https://github.com/HyperSuprime-Cam/hscPipeBase/blob/master/python/hsc/pipe/base/matches.py] which adds functions to generate "unpacked matches" in a Catalog (and vice versa).  It will be ported into {{lsst.afw.table}}.    The port includes following HSC commits:  *Add functions to generate 'unpacked matches' in a Catalog.*  https://github.com/HyperSuprime-Cam/hscPipeBase/commit/210fcdc6e1d19219e2d9365adeefd9289b2e1186    *Adding check to prevent more obscure error.*  https://github.com/HyperSuprime-Cam/hscPipeBase/commit/344a96de741cd5aafb5e368f7fa59fa248305af5    *Some little error handling helps.*  https://github.com/HyperSuprime-Cam/hscPipeBase/commit/61cc053b873d42802581adff8cbbdb52a348879e  (from branch: {{stage-ncsa-3}})    *matches: add ArrayI to list of field types that require a size*  https://github.com/HyperSuprime-Cam/hscPipeBase/commit/d4ccd11d8afbcdd9cf0b35eba948cca4b5d09ba5  (from branch {{tickets/HSC-1228}})    Please also include a unittest.
Answer: 27653.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "To wit:    {code}  $ flex --version  flex 2.6.0    $ bash newinstall.sh    LSST Software Stack Builder  [...stuff...]  eups distrib: Failed to build doxygen-1.8.5.eupspkg: Command:   source /Users/jds/Projects/Astronomy/LSST/stack/eups/bin/setups.sh; export EUPS_PATH=/Users/jds/Projects/Astronomy/LSST/stack; (/Users/jds/Projects/Astronomy/LSST/stack/EupsBuildDir/DarwinX86/doxygen-1.8.5/build.sh) >> /Users/jds/Projects/Astronomy/LSST/stack/EupsBuildDir/DarwinX86/doxygen-1.8.5/build.log 2>&1 4>/Users/jds/Projects/Astronomy/LSST/stack/EupsBuildDir/DarwinX86/doxygen-1.8.5/build.msg  exited with code 252    $ grep error /Users/jds/Projects/Astronomy/LSST/stack/EupsBuildDir/DarwinX86/doxygen-1.8.5/build.log  commentscan.l:1064:55: error: use of undeclared identifier 'yy_current_buffer'  commentscan.l:1126:58: error: use of undeclared identifier 'yy_current_buffer'  {code}    Builds fine using {{flex 2.5.35 Apple(flex-31)}}."
Answer: 222.0

User story: "Currently new technotes are created with [lsst-technote-bootstrap|https://github.com/lsst-sqre/lsst-technote-bootstrap] and cookiecutter. It’s time to make technote authoring *even easier* by creating a custom tool to automate more of the process. This is the role of {{techno}}, and this ticket will create the first subcommand in {{techno}}.    This ticket will    1. Create the {{techno}} Python project  2. Create an {{init}} command that uses {{cookiecutter}}’s python api, dynamically suggests the current date, and creates a repo on GitHub."
Answer: 679623.0

User story: "Harvest metadata about records in a Zenodo Community collection using the {{oai_datacite3}} format. See https://zenodo.org/dev    Part of the [zenodio|https://github.com/lsst-sqre/zenodio] Python package. This tool will be used by our technote and the documentation indexing platforms."
Answer: 11487.0

User story: "Learn more about orchestration, task execution, and logging.  "
Answer: 1.0

User story: K-T suggested that I take my list of "stack deficiencies and suggested improvements" [https://confluence.lsstcorp.org/display/SQRE/Stack+Deficiencies+and+Suggested+Upgrades] on confluence and (with Tim J.'s help) create tickets for each item (as much as possible) so that the work could be scheduled.  
Answer: 7.0

User story: "Plan and write a technote outlining communication and documentation platforms from a DM perspective. The technote will specify    - how each platform is used  - what developments need to be done  - address integrations with LSST-wide communications projects  - address information architecture (generally, the ease of discovering the right information)"
Answer: 120989.0

User story: "weekly LSST local grouop meetings, NCSA meetings (All-hands, software, etc), code review, other local meetings, postdoc meetings and tasks"
Answer: 2718.0

User story: "Verification dataset meetings, RFD meetings, DES Chicagoland meeting and preparation"
Answer: 12.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "During the processing of the COSMOS data for the verification dataset work I ran many jobs of processCcdDecam.py on the new linux server, bambam.  The performance was very slow, 4x longer than running a single job at a time.  Figure out what is going on."
Answer: 1405.0

User story: "The EventAppender needs to add host identification (host/process/id) information to the log message it transmits.   This was inadvertently left out."
Answer: 105365.0

User story: "Create a prototype standalone validation test of the astrometric performance of the stack on suitable CFHT data.  Module is called `validate_drp`     http://github.com/lsst/validate_drp_cfht    Decide how those data should be provided (testdata_cfht being one obvious possibility), and determine if obs_cfht tests and the tests for this validate_drp module should use the same test datasets.    This is prototyping for DM-2518."
Answer: 42329.0

User story: "Incorporate the astrometry test as an optional component in lsst_dm_stack_demo.    This is chosen because lsst_dm_stack_demo currently serves as the very loose stack validation and understanding how to do astrometric repeatibility testing in this demo will help explore how it would make sense to put in a fuller CFHT validation test of the DM stack."
Answer: 38306.0

User story: "Adapt the CFHT astrometry validation test to the DECam reprocessing effort.      Will focus on the repeat observations of the COSMOS field.  Goal is to just do a simple two-observation comparison.  Doing a full test of all of the observations will be a later story.  "
Answer: 53001.0

User story: "Understand, re-rerun, and recreate clean version of [~<USER> 's CFHT astrometry test for the astrometry RMS for two sample CFHT observations.  This test is on the NCSA machines in  /lsst8/<USER>valid_cfht    Create a repository for this test with an eye toward it becoming integrated in a validation suite for the stack.        "
Answer: 59586.0

User story: "The task that takes care of measurement and calibration on characterized images will be promoted to a command line task.  As with the other command line tasks, it should be possible to run the calibration and measurement command line task on data without necessarily running IsrTask or CharacterizeTask.    Of course, this means the task will have to get a PSF from somewhere, see [clo|https://community.lsst.org/t/requirements-for-overhauled-calibration-task/370] for suggestions."
Answer: 148101.0

User story: "In refactoring the processCcd.py script, we'd like to make each component callable by command line as well.  This is to promote the image characterization task to a command line task.  A requirement will be that this task be able to run on data without IsrTask having been run (command line tasks should be insulated as much as possible from knowing about previous processing)."
Answer: 148105.0