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: "Currently {{template}} (that generates the {{StorageHint}}) is stored in {{Registry}}. Move this to the {{Datastore}} configuration as an override for a generic {{template}} (that is based on all {{DataUnit}} primary keys)."
Answer: 66165.0

User story: "Currently StorageClass subclasses (e.g. {{Exposure}}) are defined in code. Move these to YAML configuration (e.g. as done for {{Formatter}})."
Answer: 10169.0

User story: "If an eups distrib tag is generated/pushed by either by {{release/run-publish}} or {{releaes/tarball}}, which is later manually removed from the public {{EUPS_PKGROOT}}(S), subsequent builds may republish these tags from local cached state."
Answer: 137082.0

User story: "A upgrade is needed to resolve known (but not extremely concerning) security issues and to see if it improves bluecoean UI loading times."
Answer: 7240.0

User story: "Template: The PSF-matched sigma-clipped coadd variance is computed from the variance planes of the inputs and not the empirical dispersion of the images as expected. Intuitively if we're looking for outliers, we'd want the template variance to use the dispersion of the images.          Warp: As pointed out by [~price], we'd also want to scale the variance in the warps for the same reason we scale the variance on coadds before detection on coadds. "
Answer: 1636.0

User story: "In order to facilitate work on the Datastore prototype the existing code should be refactored a bit."
Answer: 432.0

User story: "Use overlay instead of devicemapper for storage."
Answer: 76151.0

User story: "The fitting of radiative transfer model on the spectrometric data are at the level where a signal could be caught (illustration), so I'll go for a first try at realtime synthetic photometry     "
Answer: 213542.0

User story: "[~<USER> noticed that centroids and shapes aren't being measured in {{forcedPhotCcd}}. They should be, since they are potentially useful (e.g., centroids are good for proper motion)."
Answer: 8708.0

User story: "This ticket is similiar to DM-13333, except that instead of looking at cells, I will use simulated footprints and compare the depth for different cell sizes and boundaries.  Additional complexity comes in when a footprint crosses a cell boundary.  In this case, we need to find the combined set of visits from the overlapping cells that do not cross any boundaries and create additional coadds.  Report numbers on how many more coadds this would lead to."
Answer: 248765.0

User story: "For now, 2 kubernetes clusters will be created for each half od the cluster."
Answer: 22329.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: "As shown in DM-10823, we can achieve good accuracy on shear measurements working from the coadds instead of doing a multi-epoch fit.  To create a valid PSF for the coadd we need to reject epochs where the object falls on the edge of a CCD.  In practice this could be done by doing a per-object coadd, but this requires keeping all the images in memory.  This ticket is to investigate the loss in depth by rejecting all images in a coadd that cross a CCD edge.  This would remove the need to do a per-object coadd.  This will depend the size of a region that is coadded and potentially the dither strategy."
Answer: 248812.0

User story: "Use ID, per [https://api.slack.com/changelog/2017-09-the-one-about-usernames]     "
Answer: 1462.0

User story: "We need to have a set of realistic footprint sizes to study how these may be affected by coadding.  This could include data from HSC or perhaps from simulations such as https://github.com/LSSTDESC/WeakLensingDeblending."
Answer: 143701.0

User story: Add per slack user {{@}} notifications to the jenkins pipeline "notify" utility library using the newly created {{ghslacker}} micro-service.
Answer: 1364.0

User story: "Variation of seeing and error on the wavelength solution does shift the equivalent width measurement by several %.    The solution is in the illustration !     "
Answer: 214883.0

User story: "The current status of dispersed image analysis is presented in several documents attached to Harvard meeting webpage     https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73566653"
Answer: 214957.0

User story: "Three NCSA staff members attend & participate in the Middleware Design/Hack Week, January 22-26, 2018 at Princeton.    https://confluence.lsstcorp.org/pages/viewpage.action?pageId=68584672"
Answer: 12842.0

User story: "{color:#000000}Begin Investigate into alternate methods for copying files, service endpoints that could be placed in front of storage to receive files. While potential exists for immediate use, this is more for potential use in the longer term.{color}"
Answer: 103572.0

User story: "Add authentication to the service endpoints for dedicated LDAP group(s)"
Answer: 105173.0

User story: "{color:#000000}Assemble and configure components of the file transfer service endpoints, ensuring webdav server and prototype ingest/saving code interoperate in delivery area. Coordinate service account features as needed.{color}"
Answer: 105191.0

User story: "REmoving ReplyChannel would simplify the code."
Answer: 23456.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: Correct and re-organize catalog-data selection screen on PDAC Portal for WISE single-epoch source data.    Under the "LSST Data" button and the "Search" tab that appears beneath it, there will be a "Select Project" dropdown, as now. That dropdown should have three selections:    (1) "SDSS Stripe 82, 2013 LSST Processing"       (Note that currently there is a typo: "SSDS".)        This should remain unchanged, except for the more descriptive title.   In particular, we retain the "Catalogs" and "Images" radio buttons.        If possible, we could add, lower down on this panel (i.e., below all the radio buttons), an "open in new window" link to https://confluence.lsstcorp.org/display/DM/Properties+of+the+2013+SDSS+Stripe+82+reprocessing with the text "Documentation on the Stripe 82 reprocessing dataset".     (2) "AllWISE Processing of WISE pre-hibernation (2010-2011)"       Under "Catalogs" we would have three radio buttons:       o AllWISE Source Catalog (comparable to LSST Object)       o AllWISE Multiepoch Photometry Table (comparable to ForcedSource)       o AllWISE Reject Table (no LSST analog)        Under "Images" we would have exactly what is there now in the version deployed on PDAC.        Below all the selectors, add an "open in new window" link to http://wise2.ipac.caltech.edu/docs/release/allwise/expsup/ with the text "Documentation on the AllWISE dataset".     (3) "WISE & NEOWISE Single-Epoch Photometry (2010-2014)"        Under "Catalogs", there should be four radio buttons:        o WISE All-Sky Single Exposure (L1b) Source Table        o WISE 3-Band Cryo Single Exposure (L1b) Source Table        o WISE Post-Cryo Single Exposure (L1b) Source Table        o NEOWISE-R Year 1 Single Exposure Source Database        Under "Images" we should have what is currently there under "wise_00"'s Images section, except for removing the AllWISE Atlas Images radio button.        When "Images" is selected, below the three available radio buttons, add the note "(Single-epoch images for the NEOWISE Reactivation mission are not currently available on the PDAC.)"        Below all the selectors, add an "open in new window" link to http://wise2.ipac.caltech.edu/docs/release/neowise/expsup/ with the text "Documentation on the NeoWISE data releases"    
Answer: 1416.0

User story: "Add summary and conclusions regarding suitability of Kafka to alert distribution system needs to DMTN-028."
Answer: 95127.0

User story: "Run alert stream distribution benchmarking tests using multiple partitions configuration for Kafka.  Results to be added to DMTN-28"
Answer: 73330.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: "From image per image analysis of the 3 nights of spectrometric and photometric observation, it appears that the determination of the positions and flux at the edges of an Equivalent Width is the dominant source of uncertainty (~5-10%).    -> A second order polynomial fit on a carefully selected interval (not spectral features) does reduce the dispersion by a factor of 2-3.    Slides 11, 12 and 13 show illustrations of the question.    [^spectroVSphoto.pdf]"
Answer: 217460.0

User story: "There's no `w_2018_03` tag at https://eups.lsst.codes/stack/src/tags/?C=M;O=D."
Answer: 4436.0

User story: "I've been getting segfaults when running {{pipe\_tasks/tests/nopytest_test_coadds.py}} on OSX (with clang). {{lldb}} backtrace points to a python destructor, so I suspected memory problems. I ran valgrind on Linux (yes: different OS, different compiler, but I thought it might help anyway) and identified several problems in LSST code. There are also many python issues ({{invalid read}}, {{Conditional jump or move depends on uninitialised value}}, etc), but there are LSST-specific problems in {{ast}}, {{lsst::afw::fits}}, {{lsst::afw::table}}, and {{lsst::meas::base:: GaussianCentroid}}."
Answer: 38508.0

User story: "The requirements associated with Level 2 in LDM-148 (and those referenced in the Level 2 test spec document) need to be explicitly copied into LDM-562."
Answer: 539730.0

User story: Check that results still agree with HSC results. No longer have have to be identical, but if not, should be a) consistent, and b) ideally an improvement.      Check that it runs on other cameras, and that results agree with current knowledge, e.g. SAWG data, mainly on LSST sensor and raft datasets.      For example, the gradient of the co-variance wrt lag      Residuals as a function of magnitude if on-sky data exists (not for LSST).    IF, in the "unlikely" event that results here disagree with SAWG data, another ticket will be filed to get to the bottom of that.
Answer: 254951.0

User story: "Make optional plots of things that are done along the way:       * PTC curve and its fit       * Write out the diff images and ISR images as an option       * Add afwDisplay debug options   Maybe also add warnings here for things that might be out of range"
Answer: 136363.0

User story: "This is mainly refactoring as currently lots of code is duplicated.      * Add full camera agnosticism, will need to run ISR tasks from the obs_package, from outside ISR          * Probably define this in each obs_package as a config option as to which ISR task to target (default or own)      * Possibly also speed-up slow bits if things are being done too inefficiently"
Answer: 381556.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: "Code found in DM-5082.    Stackify:      * make a task that runs      * give it a config      * Rename variables and methods in keeping with stack conventions      * Make print statements into logger warnings etc      * Then, check results still match    NB: This code NEED NOT COMPLY WITH ALL STACK STANDARDS    It will be cleaned up in the next ticket."
Answer: 109031.0

User story: "Run code attached to DM-5082 as-is, reproduce results   * gather data on tiger   * run with correct version of stack   * check against Will's results"
Answer: 10360.0

User story: "Discuss porting of BF measurement code with Will Coulton and <USER>to better understand the code, and requirements for porting, and better plan and time-estimate the upcoming work"
Answer: 1.0

User story: "SsiSession is currently deleted by a call to Finished, and this can happen before tasks using the object are all done with it, causing a segfault and worker crash. Moving the the UnBindRequest call to the destructor and using a shared pointer for the SsiSesion object should make it safe. Also, it looks like eliminating the SsiSession::ReplyChannel class will make the code simpler, but some changes need to be made to expose the functions ReplyChannel calls in xrdssi."
Answer: 5503.0

User story: "The new `dcrAssembleCoaddTask` iterates over the outputs of its `assemble` method, which requires overriding the `run` method of the base `assembleCoaddTask`. This ticket and branch of `pipe_tasks` is to explore modifying the base `run` method to always iterate over the outputs of `assemble`. If that works cleanly, we will consider merging the branch, but it is possible it will instead be discarded."
Answer: 17363.0

User story: "Change {{DataUnit}} (and its derived classes) in the Butler prototype to be a hierarchy of classes whose instances represent {{DataUnit}} _tables_ rather than the rows of those tables. We will instead typically use plain {{dict}} objects (called {{DataID}} by analogy with the Gen. 2 Butler concept) to represent the rows of {{DataUnit}} tables."
Answer: 187208.0

User story: "hipsSurveysId has some issues:   * It does not work when you load a HiPS with a URL via API   * I am not sure it should be in WebPlotRequest at all.    [~<USER> and [~<USER> need to review what it is doing and discuss the best way to implement it.    After the discussion implements the changes and fix any bugs."
Answer: 49689.0

User story: "{color:#000000}Write the milestone test verification report.{color}"
Answer: 218926.0

User story: "{color:#000000}Run verification tests. Assumes corrections to code and processes as necessary.{color}"
Answer: 141222.0

User story: "{color:#000000}Work with Data Facility staff to write the test specification document for the Spectrograph milestone.  {color}"
Answer: 218923.0

User story: "{color:#000000}Prototype code to save raw files from the test stand to the NCSA delivery area. This is the code that will be used during the milestone tests.{color}"
Answer: 111142.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: "{color:#000000}Initial version of code to save raw files from the test stand to the NCSA delivery area.{color}"
Answer: 89549.0

User story: "{color:#000000}Prototype code to ingest files from the NCSA delivery area to the Data Backbone. This is the code that will be used during the milestone tests. {color}"
Answer: 111144.0

User story: "{color:#000000}Initial version of code to ingest files from the NCSA delivery area to the Data Backbone.{color}"
Answer: 20505.0

User story: "{color:#000000}Work with system and development staff to detail needs for the Data Backbone test system(s), accounts, etc.{color}"
Answer: 111197.0

User story: "[~price] has reproduced some strange data features at Princeton that had been reported by [~<USER>.  Poke at this data with the interactive QA tools I have been developing to see if they can help diagnose what is going on, or at least to reproduce/match the topcat-style workflow that [~price] has heretofore used to investigate questions like this.    This involves setting up a QA environment equivalent on {{tigressdata}} to what I've been using on {{lsst-dev}}, running the pipe_analysis scripts (in parquet-only mode) on the data ({{/tigress/HSC/HSC --calib /tigress/HSC/HSC/CALIB-LSST-20170105 --rerun hscPipe-6.0-beta4/20180116/sxds}}), and putting together an investigatory notebook."
Answer: 77100.0

User story: "Upgrade webpack to version 3 (currently v1)    Babel is at the current version, just review the presets to make sure they are still what we want.    TG 03/01/2018:   - Modified buildScript/webpack.config.js according to [https://webpack.js.org/guides/migrating/]   - Updated the related libraries (webpack 3.x babel-loader 7.x | babel 6.x)   - Updated Babel to[ use preset|https://babeljs.io/docs/plugins/preset-env/] env for the two latest versions of Chrome, Safari, Firefox, and Edge. The result is that the ES6 code will be transformed into ES5 only if a feature is not supported by one of the browsers. This results in smaller minified file size.   - Updated eslint and the related plugins   - Updated firefly_loader.js to use anonymous self-calling function   - Fixed bugs exposed by the new build procedure. (See PR for more info.)"
Answer: 58847.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: "We decided to change how SQUASH handles the data blobs produced by the verification jobs. This is motivated by the performance issues seen in DM-13259 pushing the HSC test dataset to the new SQuaSH API.    In this implementation the full verification job will still be sent to the SQuaSH API, the measurements and metadata will be stored in the MySQL database while the data blobs will be uploaded to an S3 bucket and the corresponding reference (the S3 object URI) will be kept in the database. We are also uploading the whole job document to S3 to have the source of truth around in case it is needed for a future refactoring.    This change goes in the direction of the Data Butler composite datasets and is a shim while we don't have that functionality in place.     It is also interesting from the point of view of data access an visualization in SQuaSH. We could transform and store these data blobs in a more appropriate format such as {{parquet}} instead of retrieving them in JSON from the REST API as we do now.               "
Answer: 10186.0

User story: "* React needs to be updated to version 16.  We should also update other js libraries as well.   * We should also upgrade plotly   * This following is the list with my initial guesses whether we should upgrade.     +package.json list+     enum - yes  fixed-data-table-2 - yes  highcharts - no  immutability-helper - yes  isomorphic-fetch - yes  local-storage - yes  lodash - yes  numeral - yes  point-in-polygon - yes  prop-types - yes  rc-slider - yes  react-color - yes  react-component-resizable - yes  react-grid-layout - yes  react-highcharts - no  react-sizeme - yes  react-split-pane - yes  redux - yes  redux-logger - yes  redux-saga - yes  redux-thunk - yes  shallowequal - yes  transformation-matrix-js - yes  validator - yes  classnames - yes  react-dnd - yes  react-dnd-html5-backend - yes  moment - yes"
Answer: 50006.0

User story: "From the difference between jointcal's internal fit metrics and those computed by pipe_analysis and validate_drp, it appears that the persisted astrometry model may be incorrect. I don't have any unittests that explicitly check this, and I've been meaning to write some. Now's the time."
Answer: 127026.0

User story: "Create an ETL pipeline for LaTeX-based documents published as Lander landing pages. This is similar to the work done for reStructuredText-based technotes in DM-13188.    Because metadata for LaTeX documents is computed at build time from the source (i.e., it required a checked-out Git repo), it makes sense to publish a JSON-LD document at build time as well.    The choices are either to add the JSON-LD as a {{script}} tag in the landing page itself, or add a {{metadata.jsonld}} document alongside the HTML, but in a separate file.    Then an ETL pipeline run from {{lsst-projectmeta-kit}} itself would ingest this data and load it into MongoDB, as we're already doing for reStructuredText-based technotes."
Answer: 38484.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: "I made a number of cleanups of method names in DM-9071, in this commit:    https://github.com/lsst/jointcal/commit/9efc5d23808b5e6f33d69e7ccd9bcf6c0bc844cb    These should be picked out of that ticket and pushed to master."
Answer: 453499.0

User story: "The fitter chi2 contributions debug output files need to be cleaned up and improved so we can do direct comparisons of jointcal's internal model, pre- and post-fit. Also have to make some plots to test that the output is good."
Answer: 38852.0

User story: I will read the manuscript:       "SCARLET: Source separation in multi-band images by Constrained Matrix Factorization"   <USER> <USER> Maximilian Jerdee, Robert Armstrong, Ai-Lei Sun, James Bosch, <USER>   in its entirety and provide any feedback I have, but I have been asked to pay particular attention to *Section 3: Applications*.         Note that this review is considered a "Science Pipelines" internal review (and is separate from the LSST-internal reviews being carried out and tracked on PUB-56).
Answer: 8214.0

User story: "Create a presentation to give the Princeton software group an update on the new deblender, which is likely to be implemented in the stack as part of the current epic."
Answer: 7093.0

User story: "The author field for this document is incomplete."
Answer: 4.0

User story: "Add a use case and requirement that describes the need for the {{Butler}} to have the ability to persist the data blobs associated with a {{Job}} and the JSON file that describes the {{Job}} in different datastores.  For example the blobs may be placed in an object store with the {{Job}} could be ingested in a JSON aware SQL database."
Answer: 1613.0

User story: hscPipe 6.0-beta5 will include the following important features and bug fixes:  * DM-12664: PsfMatched slivers of calexps are worthless  * DM-12995: Improve detection thresholds and background with temporary sky objects  * DM-13146: Update HSC defects  * DM-13182: SpanSet.fromMask produces larger spans than image  * DM-13227: Refine exposure-wide background subtraction  * DM-13260: Support construction of new HSC calibs  * DM-7588: Update MPICH  * DM-13345: Improve template and warp variance for Warp Compare  * DM-13408: Fix fringe fix  * DM-13396: Fix mask propagation on coadds  * DM-13388: Enable visit-level sky subtraction for HSC by default  * DM-13389: Enable transmission curve attachment for HSC by default    Additional features/fixes that we might want:  * DM-13148: Support Suprime-Cam  * DM-13244: Port parallel ingest from HSC  * DM-11776: "RuntimeWarning: invalid value encountered in greater/less" in processing HSC data  * DM-13380: Add base_PixelFlags_flag_inexact_psfCenter
Answer: 21303.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: "When building biases, I get:  {code}  24149 WARN  2018-01-17T16:11:05.104-0500 bias: Unable to process DataId(initialdata={'field': 'BIAS', 'dateObs': '2015-05-19', 'pointing': 1234, 'filter': 'HSC-Y', 'visit': 29878, 'ccd': 61, 'taiObs': '2015-05-19', 'expTime': 0.0}, tag=set()): [Errno 2] No such file or directory: '/tigress/HSC/HSC/CALIB-20180117/STRAY_LIGHT/ybackground-061.fits'  application called MPI_Abort(MPI_COMM_WORLD, 1) - process 66  {code}    It's trying to do the y-band stray light correction, which it shouldn't for a bias or dark."
Answer: 17107.0

User story: "{{validate_drp}} was recently ported to the new verification framework (-DM-12253-) however no results are sent to SQuaSH because a redesign of the RESTful API was needed (-DM-12194-).     The SQuaSH API was reimplemented in Flask and we deployed a demo instance that can be used to exercise the full pipeline.    [https://squash-restful-api-demo.lsst.codes|https://squash-restful-api-demo.lsst.codes/]    For that,  {{dispatch_verify}} must be enabled in the Jenkins pipeline.    Assuming you have a verify job JSON document, you can execute {{dispatch_verify}} from the {{lsstsw}} folder like so:       {code:java}    $ dispatch_verify.py --url https://squash-restful-api-demo.lsst.codes --user <user name>  --password <passwd> --env jenkins --lsstsw $(pwd) Cfht_output_r.json  ---  verify.bin.dispatchverify.main INFO: Loading Cfht_output_r.json  verify.bin.dispatchverify.main INFO: Refreshing metric definitions from verify_metrics  verify.bin.dispatchverify.main INFO: Inserting lsstsw package metadata from /Users/<USER>Projects/lsstsw/lsstsw.  verify.bin.dispatchverify.main INFO: Inserting Jenkins CI environment metadata.  verify.bin.dispatchverify.main INFO: Uploading Job JSON to https://squash-restful-api-demo.lsst.codes.  verify.squash.get INFO: GET https://squash-restful-api-demo.lsst.codes status: 200  verify.squash.post INFO: POST https://squash-restful-api-demo.lsst.codes/auth status: 200  verify.squash.post INFO: POST https://squash-restful-api-demo.lsst.codes/job status: 201     {code}       "
Answer: 148088.0

User story: "Reprocess the two WIDE tracts of the HSC RC1 dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], and the three tracts of the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_04. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (--DM-10129--/--DM-11020--)."
Answer: 28999.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: "Here [^spectroVSphoto.pdf] is an update of the comparison of spectrometry and photometry acquired during the same period of time (repeated photometry on lp995-86 during 3 consecutive nights while targeting with spectrometry hip107120 hip8417 hip113896 hip17819 hip19796 hip96536 hip26382).     In i-band, there is a possibility for variations induced by the atmosphere (slide 5), so I tried to correlate that with PWV EW.  The conclusion is that the PWV EW measurement is still not precise enough (slide 6).  Also note that the result does not depend on the targets, which is encouraging."
Answer: 224944.0

User story: "Scott Carlsten (DM-12876) started looking into using different seeing in each band and its effects on PSF/model magnitudes to distinguish between stars and galaxies. Look into this further."
Answer: 22959.0

User story: "A design discussion for HiPS images display.    Doodle pool:    https://doodle.com/poll/v9vf8wzueeedzvt7"
Answer: 50521.0

User story: "Experiment with a simple way to filter alert data in Python using sims data."
Answer: 125331.0

User story: "At the [DMLT face to face meeting in November 2017|https://confluence.lsstcorp.org/display/DM/DM+Leadership+Team+Face-to-Face+Meeting%2C+2017-11-01+to+03] it was requested that the Level 1 requirements in DMSR (as defined by LDM-148) be flowed down into LDM-602 to seed the L1 System Requirements. This ticket is to do that flowdown in the MagicDraw model and to issue a first draft of LDM-602."
Answer: 544063.0

User story: "DMTN-056 is currently out of sync with the state of the Butler prototype. Bring both back in to sync. Also incorporate some minor naming changes (e.g. {{tag}} to {{collection}}) that were discussed in person."
Answer: 4061.0

User story: "This ticket is to use the projectmeta MongoDB dataset created in DM-13188 and use it to populate the https://www.lsst.io landing page.    The projectmeta DB currently only includes reStructuredText-based technotes.    This data will be presented on a single page, likely, so I don't have to settle on a more general info architecture for the site."
Answer: 3127.0

User story: "HSC used to have a script {{hscIngestImagesParallel.py}} which ran ingest in parallel (using what is now ctrl_pool), making ingest of many images go much faster. Port this functionality to LSST."
Answer: 1723.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: There was an incident reported by [~<USER> on slack:     {quote}  I did a count(*) on LSST20 and it gave me back real data and columns for the result …      [3:31]    ```[vthukral@ccosvms0070 in2p3]$ time mysql --host ccqserv125 --port 4040 --user qsmaster LSST20 -e "SELECT COUNT(*) FROM Object;";  +--------------------+---------------------+---------------------------+----------------------------+-----------------------------------+------------------------+------------------------+------------------------+  | ra                 | decl                | raVar                     | declVar                    | radeclCov                         | u_psfFlux              | u_psfFluxSigma         | u_apFlux               |  +--------------------+---------------------+---------------------------+----------------------------+-----------------------------------+------------------------+------------------------+------------------------+  | 284.98083849415934 |  -63.32859963197394 |       0.03588015008077164 |        0.04575243321809053 |       0.0000000012152185681231455 |  7.396697501646931e-30 |  9.604600362557029e-31 |  9.647062881997884e-30 |  ```  (and many more rows)  {quote}    and Igor dug out this from the log:  {noformat}  [2018-01-13T00:27:12.724+0100] [LWP:503] DEBUG rproc.InfileMerger (core/modules/rproc/InfileMerger.cc:264) - Merging w/CREATE TABLE result_364646 ENGINE=MyISAM SELECT SUM(QS1_COUNT) FROM result_364646_m  [2018-01-13T00:27:12.746+0100] [LWP:503] ERROR util.Error (core/modules/util/Error.cc:50) - Error [1050] Error applying sql: Error 1050: Table 'result_364646' already exists Unable to execute query: CREATE TABLE result_364646 ENGINE=MyISAM SELECT SUM(QS1_COUNT) FROM result_364646_m  [2018-01-13T00:27:12.746+0100] [LWP:503] ERROR rproc.InfileMerger (core/modules/rproc/InfileMerger.cc:342) - InfileMerger error: Error applying sql: Error 1050: Table 'result_364646' already exists Unable to execute query: CREATE TABLE result_364646 ENGINE=MyISAM SELECT SUM(QS1_COUNT) FROM result_364646_m  {noformat}    This looks like there was a leftover result table whose name was reused for new query (this could happen when someone resets QMeta autoincrement ID).    Qserv should handle this situation better, there should be an error returned to user in that case, not data from old result table (or leftover table should be deleted).
Answer: 8554.0

User story: "This covers the regular maintenance of community.lsst.org to upgrade it from Discourse v1.9 to v2.0."
Answer: 3.0

User story: "Make sure {{dispatch_verify}} works with the new SQuaSH API, for example authentication is done via JWT token now. See an example here [https://github.com/lsst-sqre/squash-rest-api/blob/master/tests/test_api.ipynb]    We need new methods in {{lsst.verify}} to get the access token from the SQuaSH API and make an Authorization header."
Answer: 1617.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: "Now that the [new API is alive|https://squash-restful-api-demo.lsst.codes/] we need the following resources that are consumed by the SQuaSH bokeh apps:   * measurements ->  monitor app   * code changes -> monitor app   * stats -> dashboard initial page   * blobs > AM1, PA1, etc apps     NOTE: the performance on retrieving the data from the new implementation will be evaluate only after DM-12604 is done"
Answer: 28762.0

User story: "The reason for it is illustrated in the pdf         [^spectroVSphoto.pdf]"
Answer: 226317.0

User story: "Headless service will set up a constant DNS name for all Qserv nodes. This will allow to ease configuration."
Answer: 15888.0

User story: "Build on the tools created in DM-13152 to make easy QA image browsing even easier, using a bokeh server web app."
Answer: 482433.0

User story: DM-10729 implemented one way of writing back out to a catalog prior to RFC-322 being implemented, that introduced a {{_calFlux}} field for the {{outField}}. {{_calFlux}} isn't used elsewhere in the stack, and is inconsistent with the documentation.    This ticket is to change it to write to {{outField+"_flux"}}, which allows writing the calibrated fluxes back to the same field (by having {{inField==outField}}), which is consistent with what meas_mosaic is currently doing.
Answer: 4605.0

User story: "Upgrade esutil to 0.6.2.5 which fixes python3 compatibility bugs."
Answer: 8245.0

User story: "The exposure-wide background subtraction ({{skyCorrection.py}}) can leave large negative residuals around bright sources when used with HSC (which sets the background scale to 1024 pixels). This can be mitigated by doing a more careful detection of faint extended structure, which was present in the prototype from NAOJ."
Answer: 15747.0

User story: MagicDraw enforces alphabetic order for requirements (within a package).  This makes it impossible to define the order of the requirements as they appear.    The existing SuperTask requirements in LDM-556 were written without realizing this and contain references to previous requirements as "above".    It is desirable for requirements to be meaningful in isolation in any event, so this task is to clean up the language and avoid positional references.
Answer: 157273.0

User story: "Python 3 is now the default for the stack, and in the future only Python 3 will be supported.  FGCM (both the LSST stack code and the third-party module) need to be updated for python 3 support.  "
Answer: 18317.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: "Seeing a future warning emanating from meas_deblender when running SourceDeblendTask:  {code:java}  /opt/lsst/software/stack/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_deblender/14.0-1-g8b7e855+32/python/lsst/meas/deblender/plugins.py:455: FutureWarning: `rcond` parameter will change to the default of machine precision times ``max(M, N)`` where M and N are the input matrix dimensions.  To use the future default and silence this warning we advise to pass `rcond=None`, to keep using the old, explicitly pass `rcond=-1`.   X1, r1, rank1, s1 = np.linalg.lstsq(Aw[:, :NT1], bw){code}       Harmless for now, however our demo/tutorials trip it numerous times so it would be great if we could fix it.     [~<USER> Jim told me to assign it to you, don't hate me.     "
Answer: 263219.0

User story: "The butler gen 3 requirements were reviewed in December 2017. This ticket is for implementing the requested changes."
Answer: 181295.0

User story: "When galsim is installed with a binary installation from eups distrib its table file lacks a prepend statement to add an LSST_LIBRARY_PATH entry. This causes things built against galsim to fail. This ticket should make the installer add in the appropriate LSST_LIBRARY_PATH entry"
Answer: 994056.0

User story: "The shared stacks on lsst-dev01 (and Tiger & Perseus, for the Princeton crowd) should be updated to install 2018-vintage weeklies. This should just be a matter of tweaking the regexp."
Answer: 1396.0

User story: "When the deblender was updated to use different size boxes for all objects, the {{recenter_sources}} method was modified to fit each sources position separately. This might be the reason behind some faint sources that we see drifting during the fit, so this ticket will update the {{recenter_sources}} method to project each source onto the full model so that the positions can be updated simultaneously again."
Answer: 11529.0

User story: "I have installed my stack using the eups distrib binaries. Today I went to rebuild the meas_extensions_hsm package which links to the galsim package, and the build failed. It complained about not being able to find libgalsim.dylib in the galsim package. Upon looking in the directory for galsim I see:    {code}  _-rwxr-xr-x  1 nate  staff  3289320 Dec 13 10:12_ _libgalsim.1.5.dylib_  _lrwxr-xr-x  1 nate  staff      190 Dec 13 10:12_ _libgalsim.dylib_ _-> /Users/square/jenkins/workspace/release/tarball/osx/10.9/clang-800.0.42.1/miniconda3-4.3.21-10a4fa6/build/stack/miniconda3-4.3.21-10a4fa6/DarwinX86/galsim/1.5.1.lsst1/lib/libgalsim.1.5.dylib_  {code}    Which shows the simlink for the dylib is still pointing to the a directory on the build system. I propose that if this cant be fixed on the packaging side that we need a program like the shebangtron that will rewrite all the simlinks"
Answer: 102482.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: "There was a bug when initializing sources whose coordinates were on the border of the image, in which case the initial box had zero length or width (depending on which side they bordered).         While fixing this bug the API was also modified to allow users to pass an arbitrary initialization function to the deblender to make it more general, and an improved algorithm was implemented for initializing bulge-disk models."
Answer: 47267.0

User story: "Look into the use of colours to separate stars and galaxies."
Answer: 73958.0

User story: "Create v14.0 versions of validation_data_(cfht|decam|hsc).         1. Update these data reference sets with a processing by v14.0 of the stack    2. Add a v14.0     "
Answer: 234775.0

User story: "To better understand why jointcal isn't producing the expected results on HSC PDR1, I need to make some plots. Fortunately, [~<USER> and [~<USER> have already done a lot of work making plots, so what I really need is to adapt some of the plots in pipe_analysis to work with jointcal's output, for both the plots comparing with a refcat and for the rerun vs. rerun plots (e.g., to compare singleFrame vs. jointcal).    If done correctly, this shouldn't affect the use of meas_mosaic output, as it and jointcal output the WCS and PhotoCalib in a compatible way now."
Answer: 626556.0

User story: "In [LCR-924|https://project.lsst.org/groups/ccb/node/1683] the LSR performance metrics were flowed down to OSS. These metrics need to appear in LSE-61 so that they can be part of the DM verification plan. It may be that the target values are not as stringent in LSE-61 as they are in LSE-30."
Answer: 1001441.0

User story: "These are the major (interrelated) issues we want to have under control before the in-person meeting; we expect in-person meeting attendees to have input in the final resolution, but we want to go into the meeting with a non-empty set of approaches we think everyone will agree to.  The current approach to preflight makes a lot of people nervous even if we haven't actually invalidated it yet."
Answer: 27277.0

User story: "These are the major (interrelated) issues we want to have under control before the in-person meeting; we expect in-person meeting attendees to have input in the final resolution, but we want to go into the meeting with a non-empty set of approaches we think everyone will agree to. The current approach to preflight makes a lot of people nervous even if we haven't actually invalidated it yet."
Answer: 23152.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: "Per email from [~<USER>:    Josh,       Robert (copied on email) is experimenting with an eups-based post install hook for the shebang fixing. Can you put the file in the requested place please?         {quote}Begin forwarded message:  *From:* <USER>the Good <[<EMAIL>|mailto:<EMAIL>]>    *Subject:* *Re: [RobertLuptonTheGood/eups] Enable eupspkg to use a sub directory for the build (#124)*    *Date:* January 5, 2018 at 14:19:19 MST    *To:* <USER><[<EMAIL>|mailto:<EMAIL>]>      Can you put this file into the root of the distro?  I.e. directly in  [https://eups.lsst.codes/stack/osx/10.9/clang-800.0.42.1/miniconda2-4.3.21-10a4fa6]    It doesn't have to be there (well, it does for now).  I think it works locally (I search local paths before remote to find it, and that's tested).  I could push the code, but I think I'll need to cache the file when pulling from the server and I haven't done that yet.     R   {quote}    A test env is needed to avoid development files from being captured in the automatic backups."
Answer: 233223.0

User story: DAX already provided the ImgServ v1, SUIT needs to be modified to use the new version.          https://github.com/Caltech-IPAC/firefly/pull/528    The purpose of this PR is to convert from [DAX ImageServ v0|https://confluence.lsstcorp.org/display/DM/Update+for+ImageServ+API+-+v0] to [DAX ImageServ v1|https://confluence.lsstcorp.org/display/DM/ImageServ+API+-+v1]   * converted URLs to work with ImageServ v1   * added unit tests to check for successful HTTP status when retrieving table and images from DAX (when DAX services are available)   * bug fix: applications with no workspace, should not initialize it   * bug fix: catalog watcher should not throw exception when center cols are missing and only corner cols are present   * bug fix: filter syntax should be {{"filterName" LIKE 'u'}}   * avoid unnecessary wrapping of DataAccessException    To run tests:  gradle -Dtest.single=LSSTDbServ :firefly:test  gradle -Dtest.single=LSSTImgServ :firefly:test
Answer: 13137.0

User story: "Following up on a discussion at the project SE-IPT meeting today, the action here is to propose specific changes to the OSS and DMSR that capture the intent of the change in LCR-786, the elimination of the Base network outage buffer and the increase in size of the Camera DAQ data buffer.    Proposed language is meant to be introduced at the Systems Engineering meeting on January 30th, 2018."
Answer: 30305.0

User story: "We often store Box2Is and Box2Ds in tables.  We should have a FunctorKey to do this to reduce code duplication.    Unfortunately we may not be able to use this actually reduce existing code duplication when code has used a different convention for naming fields (as we'd need to maintain backwards compatibility with already-persisted objects), but this should at least reduce duplication going forward.    I'm planning to do this now for DM-12370 so I can use it there."
Answer: 27692.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: "Build an ETL (extract-transform-load) workflow for reStructuredText-based technote metadata.    The metadata schema is based on the work in [https://sqr-020.lsst.io|https://sqr-020.lsst.io/] (DM-13178), leveraging standardized schema.org JSON-LD.    These JSON-LD documents will be loaded into a prototype MongoDB database and used by the [https://github.com/lsst-sqre/www_lsst_io] project to build an index of technotes."
Answer: 13429.0

User story: "The routine {{getCcdIdListFromExposures}} returns a dict keyed by a tuple constructed from {{ccdKeys}}.  Unfortunately, it actually uses a tuple constructed from {{set(ccdKeys)}} which may be in a different order.    This matters as {{CalibTask.run()}} assumes that the order is {{self.config.ccdKeys}}, the value of {{ccdKeys}} which was passed to {{getCcdIdListFromExposures}}:  {code}  dataId = dict([(k, ccdName[i]) for i, k in enumerate(self.config.ccdKeys)])  {code}    There is no need for the {{set}} call, although it's easy to confirm that there are no redundant keys in {{ccdKeys}} and we may as well continue to do so."
Answer: 5445.0

User story: "!telescopeThroughput.png|thumbnail!  Note that :    1) This is Telescope + Ronchi while CBP is open transmission.  2) The linear fit sensible up to 700 something. I haven’t added a sqrt(airmass) term yet : the points are rather scattered above 800nm  —> here are snapshots of the regressions at various wavelengths :  !948nm.png|thumbnail!  !850nm.png|thumbnail!  !753nm.png|thumbnail!!700nm.png|thumbnail!  !351nm.png|thumbnail!"
Answer: 240463.0

User story: Producing a {{SpanSet}} from a {{Mask}} resulted in {{SpanSet.getArea() > Mask.getBBox().getArea()}}, which is "impossible".    {code}  (Pdb) lsst.afw.geom.SpanSet.fromMask(mask, mask.getPlaneBitMask(config.mask)).getArea()  6611104  (Pdb) mask.getBBox().getArea()  699678  (Pdb) (mask.array & mask.getPlaneBitMask(config.mask) > 0).sum()  153623  (Pdb) mask.getBBox()  Box2I(minimum=Point2I(12345, 67890), dimensions=Extent2I(1234, 567))  (Pdb) lsst.afw.geom.SpanSet.fromMask(mask, mask.getPlaneBitMask(config.mask)).getBBox()  Box2I(minimum=Point2I(9735, 67893), dimensions=Extent2I(3841, 561))  {code}    This comes from playing fast and loose with types.
Answer: 5208.0

User story: "In LCR-1024 requirements language was added to LSE-30 to connect it to LSE-163. This ticket is for adding the derived requirements relationships from the relevant DM requirements back to LSE-30."
Answer: 5583.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: "[~<USER> when testing {{dispatch_verify.py}} with the Flask based SQuaSH RESTful API I noticed some specifications without the corresponding metric in {{verify_metrics}}    For instance:    {code:java}  {'metadata_query': {},    'name': 'release.AD3.FY19',    'tags': [],    'threshold': {'operator': '<=', 'unit': 'marcsec', 'value': 30.0},    'type': 'threshold'},  {code}    When loading the specs to SQuaSH I get:    {code:java}    {'message': 'Metric `release.AD3` not found. You must provide a valid name for the metric associated with this specification.'}  {code}    I could ignore that to get the current metrics and specifications registered in SQuaSH,  for example:    https://github.com/lsst-sqre/squash-rest-api/blob/master/app/resources/specification.py#L234    but we should enforce that specifications are consistent with metric definitions.    "
Answer: 642105.0

User story: "JSON-LD is an appealing format for describing LSST project metadata (for our documents, software, and other artifacts) because it is made for the web and because it permits a large, standardized vocabulary.    This ticket is to write up specific examples of how technotes and LDMs can be expressed as JSON-LD using schema.org and CodeMeta vocabularies.    Note that this technote is [SQR-020|https://sqr-020.lsst.io]. This work supersedes https://sqr-013.lsst.io (DM-6582)."
Answer: 18983.0

User story: "Work with users and Data Facility management to refine reports and monitoring displays."
Answer: 383020.0

User story: "Create one or more dashboards for monitoring service incident reports and requests."
Answer: 16.0

User story: "The URL https://squash-restful-api-demo.lsst.codes should redirect to https://squash-restful-api-demo.lsst.codes/apidocs"
Answer: 51.0

User story: "Right now the deployment tool is not coupled to the prepuller/hub deployment yaml creation, and it should be."
Answer: 5627.0

User story: "- Create a method for the application to configure the list containing popular HiPS data.   - Research what information to report for the HiPS data list in addition to data's type, title and url.     "
Answer: 127048.0

User story: "Right now these test data use sqlite directly. Change this to sqlalchemy (core). This serves both to familiarize myself with the data and will enable testing on different databases later."
Answer: 30413.0

User story: "Update the running kernel on all jenkins related linux nodes as a partial mitigation of the    https://spectreattack.com/    Centos 7/EL7 related links:    https://access.redhat.com/security/vulnerabilities/speculativeexecution  https://lwn.net/Articles/742919/  https://access.redhat.com/errata/RHSA-2018:0007    EC2 instances may need to be restarted regardless due to AWS patching hypervisors, so it makes sense to update the kernel at the same time.    Presumably, the jenkins OSX nodes will also need to be updated but this may be split into a separate ticket."
Answer: 220.0