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: "We would like to recommend that the DM-level policy adopted under RFC-326 be promoted to a project-level policy.  This action is to begin work on that, which might take the form of submitting an LCR advocating adopting this as an OSS-level requirement, or as a separate policy document.    The basic policy proposed is that all services facing the public Internet should use secure protocols, unless a specific, technically justified exception is adopted via formal change control and with sign-off from the ISO."
Answer: 718683.0

User story: "Implement the consensus decision on RFC-326 to state, as a DM policy, that all services facing the public Internet will use secure protocols (https:, in particular, for Web services), unless a specific technical justification for not doing so is accepted by the DM-CCB and the project ISO."
Answer: 711531.0

User story: "the filter is never None, but it can be not-set. In that case the Id is Filter::UNKNOWN."
Answer: 100.0

User story: "add daf_fmt_swift package for daf swift formatters"
Answer: 16171.0

User story: "create a stub package for swift and add it to the stack"
Answer: 16081.0

User story: "Now that the constrainedPolyModel is selectable, we should improve it to bring it closer in line with what we expect the LSST Frames model will be. This would entail switching the TwoTransfoMapping to have T1 be an affine gtransfo constrained per chip (chips don't wiggle much), and T2 be an unconstrained polynomial (to nominally take out the variable sky component plus the optics, which we'll constrain later).    This may be as simple as swapping the models and where the constraint is defined. It would be very useful to have better plotting tools available to inspect the resulting models, and also possibly to have AST persistence available so we aren't having to squash the result into a TAN-SIP."
Answer: 449247.0

User story: "The dcrCoadd dataset type needs to be compatible with existing tools and functions that process coadds. "
Answer: 19960.0

User story: "Take the JSON output of a {{validate_drp}} run and produce a report suitable for a Characterization Metrics Report.    See, e.g.,     https://pipelines.lsst.io/metrics/v13_0.html#metrics-v13-0    https://github.com/lsst/pipelines_lsst_io/blob/master/metrics/v13_0.rst    and the attachment for an example to how to format things.      "
Answer: 122380.0

User story: "Saturated pixels are currently ignored during donut fitting, but from inspecting residual plots, this may not be enough to avoid outliers.  Instead, we should just ignore donuts with saturated pixels entirely.  This story is to add saturation rejection as an (optional) config parameter for donutSelectionTask (enabled by default)."
Answer: 60436.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 current Avro schemas in lsst-dm/sample-avro-alert (and also in ZTF's schemas) can give a warning when decoded in Spark using that says (e.g., shows up I think for all nullable fields):    {code}  [WARNING] Avro: Invalid default for field cutoutScience: null not a [{"type":"record","name":"cutout","namespace":"ztf.alert","fields":[{"name":"fileName","type":"string"},{"name":"stampData","type":"bytes","doc":"jpeg"}]},"null"]  [WARNING] Avro: Invalid default for field cutoutTemplate: null not a [{"type":"record","name":"cutout","namespace":"ztf.alert","fields":[{"name":"fileName","type":"string"},{"name":"stampData","type":"bytes","doc":"jpeg"}]},"null"]  {code}    This happens when I use Spark package com.databricks:spark-avro_2.11:3.2.0, create a SparkSession, and read data this way:    {code}  data = (sparkSession          .read          .format("com.databricks.spark.avro")          .load("ztf/with-schema/ztf_avro_packets"))  {code}    This might be because null needs to be in quotes and it isn't?  I don't know.      This story is try quotes around "null" type in default type field and see if     1) the Spark warning goes away  2) data still serializes/deserializes with plain Python modules and nullable fields   
Answer: 262328.0

User story: "Generating all of the query fragments for a near neighbor type search on the czar takes a considerable amount of time. It should be possible to send the query templates and subchunk ids to the workers and generate the queries there. "
Answer: 553444.0

User story: "The current version of IPython on the shared stack on lsst-dev is 5.1.0    Unfortunately, 5.1 introduced a nasty bug that makes it ~impossible to quit ipdb in any remotely sane manner. All versions >=5.2 fix this.    For details, see the first bullet point in the changelog for the 5.2 release on  http://ipython.readthedocs.io/en/stable/whatsnew/version5.html#ipython-5-0  "
Answer: 61470.0

User story: "Apply comments"
Answer: 6797.0

User story: "This ticket captures a minor delta removing some unused variables and adding an {{override}} to squash a few clang compiler warnings in {{afw}}."
Answer: 1336.0

User story: "These are bugs or enhancements not addressed in DM-9945.   * Selection box is sometimes gone when switching between unexpanded and expanded in API mode, while selection icons stay.   * When switching charts or going from one to multiple views in chart multiviewer, the chart is rendered twice: first with smaller height, then with the right height. Same when switching to expanded mode.   * In multiviewer, the options are shown in the chart space, not under settings icon. Expand is also per chart, not per multiviewer. In general, multiviewer in API probably needs more work."
Answer: 1666294.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> wrote on DM-10350:  {quote}  It looks like we're not running the blendedness algorithm by default. Should just be a matter of adding base_Blendendness to measurement.plugins.names for at least SingleFrameMeasurementTask (I don't think running it on SFM and forced is useful, though that doesn't stop us in other contexts). Probably best to do that in meas_base, assuming that doesn't cause trouble anywhere.  {quote}"
Answer: 175.0

User story: First attempt to run `validate_drp` on HSC data failed with the following:    {code}  [...]  818 sources in ccd 0  visit 29352  1428 sources in ccd 1  visit 29352  1322 sources in ccd 2  visit 29352  1202 sources in ccd 3  visit 29352  Photometric scatter (median) - SNR > 100.0 : 18.6 mmag  Traceback (most recent call last):    File "/home/wmwv/local/lsst/validate_drp/bin/validateDrp.py", line 98, in <module>      validate.run(args.repo, **kwargs)    File "/home/wmwv/local/lsst/validate_drp/python/lsst/validate/drp/validate.py", line 104, in run      **kwargs)    File "/home/wmwv/local/lsst/validate_drp/python/lsst/validate/drp/validate.py", line 205, in runOneFilter      photomModel = PhotometricErrorModel(matchedDataset)    File "/home/wmwv/local/lsst/validate_drp/python/lsst/validate/drp/photerrmodel.py", line 235, in __init__      matchRef)    File "/home/wmwv/local/lsst/validate_drp/python/lsst/validate/drp/photerrmodel.py", line 246, in _compute      fit_params = fitPhotErrModel(mag[bright], magErr[bright])    File "/home/wmwv/local/lsst/validate_drp/python/lsst/validate/drp/photerrmodel.py", line 132, in fitPhotErrModel      photErrModel, mag, mag_err, p0=p0)    File "/ssd/lsstsw/stack_20170409/Linux64/miniconda2/4.2.12.lsst2/lib/python2.7/site-packages/scipy/optimize/minpack.py", line 740, in curve_fit      raise RuntimeError("Optimal parameters not found: " + errmsg)  RuntimeError: Optimal parameters not found: Number of calls to function has reached maxfev = 800.  {code}    1. [X] Catch errors in computing things, recover, and do something reasonable.  2. [X] Make the fitting more robust.
Answer: 10563.0

User story: "In HSC we filter out visits that go into the coadd based on their PSF quality.  However, we found that the current cuts do not reject enough bad CCDs so that we can reproduce the same PSF quality on the coadd that we had in the S16A data.  This ticket is to adjust the cuts so that we can reproduce the same quality as before."
Answer: 1590.0

User story: "This ticket sees the creation of a new generator for landing pages of PDF (and LaTeX) documents on the web. The specs are:    - PDF is shown and linked from the landing page.  - Metadata about the document are also shown on the landing page to aid search engines.  - Landing pages are expected to be deployed on LSST the Docs and integrate with that platform's versioning system.  - Runnable from a CI environment, like Travis.  - The generator itself should be written in Python for maintainability by the LSST and Data Management organizations."
Answer: 20285.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: "Development on the new deblender has been using an older version of the stack before the new footprints were pushed. In order to complete DM-9784 it is useful to have access to the new {{Footprint}}/{{SpanSet}} API, so this ticket will update the user branch {{u/<USER>deblender}} that the holds the new deblender work to the current version of the stack."
Answer: 239.0

User story: Design API with DAX team for background search    Manage those searches properly   give user data retrieval information when the search is finished         Need to make it more general to support other async searches.    May, 2018    Per [~<USER>, in dbserv v1   • POSTing to /sync creates an async query, then sends you a 303 redirect _directly to the results,_ which are under /async/{{query_id}}/results/result, which is from the TAP specification.    • /async is currently equivalent to posting to /sync (blocking until result is available)     - it will evolve towards the TAP specification in the future.     - In the future, a post to /async would redirect to /async/{{query_id}}, which would tell you information about the asynchronous job that's executing. There's some work that needs to be done for the bookeeping of the asynchronous jobs before we can do this.       In order to provide non-blocking options, Data Access group needs to implement job history database to store job status and decide how to store query history.    Asynchronous queries will be implemented according to [TAP async|http://www.ivoa.net/documents/TAP/20180416/PR-TAP-1.1-20180416.html#tth_sEc2.2] specs.    Nov, 2018    DAX services will follow TAP 1.1 specifications, when implemented.   TAP async queries are now implemented in Firefly and can be tested at {{firefly/firefly-dev.html?__action=layout.showDropDown&visible=true&view=TestTAPSearch}}    To browse TAP schema, one case use {{firefly/demo/ffapi-tap-test.html}}    Other items, completed as a part of this ticket:   - Job description endpoint is passed to the client as a table link   - Added "Table Info" dialog, which currently displays table title and table links   - Each table link is represented by an href and a button to copy this url to the clipboard   - Added error checking and handling for DALI-style errors in VOTable and errors in async tap queries    Separate tickets should be created to add more information to Table Info dialog and for generic TAP query service.
Answer: 796831.0

User story: "Implement the API defined in DM-10854 to access user data storage to save/retrieve data."
Answer: 391146.0

User story: The branch protection+travisCI+flake8 system will soon be made available for activation on LSST repositories. I've volunteered be a non-SQuaRE person to test the process, using the jointcal repo (which has a very small list of commit users right now).    Once the "final draft" instructions are available, I'll follow them for jointcal and provide feedback to SQuaRE.
Answer: 475368.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: "Create conda binaries using b2906. Create python2 for Mac and Linux. Attempt python3 afterwards, which should work but don't spend too much time on issues with python3.    If there is trouble with sims_alertsim tests use b2910."
Answer: 586079.0

User story: "Add documentation and community post for Flake8, TravisCI and Github changes.    The developer documentation needs to be updated to include {{sqre-gtf}} use and recommended Github configuration.    Afterwards a community post needs to be made to communicate this change to DM developers."
Answer: 1444.0

User story: The proposal is to make a cluster of VMs for the study of Elastic Services deployed on a cluster outside of Nebula.   The baseline for this would be to make a "Kubernetes Cluster"     lsst-kube [ 1 – n ].ncsa.illinois.edu     where we can study the dynamic deployment of services via pods/containers, where a part of the cluster would be HTCondor and part of the Cluster would be JupyterHub services. 
Answer: 33307.0

User story: "When RA = 0, Dec = 90, WISE image, overlay the grid, you can see the line of RA=180 is missing. See attached image."
Answer: 3356.0

User story: "The lion's share of the time in instantiating a butler goes to building the camera object, because that involves parsing a {{Config}} with many lines, and a {{stat}} call for each line to get the traceback.  Multiple butler instantiations (e.g., for multiprocessing or pipe_drivers) could benefit from caching the camera once it's built."
Answer: 1371.0

User story: "React needs to be updated from 15.3 to 15.5 as preparation for the next major release.    Look at other package we use and upgrade any that are appropriate."
Answer: 3307.0

User story: "Create a repository to store data for testing {{meas_deblender}}. At present this is the simulated data generated by [~<USER> in DM-9644 but later is likely to include public HSC data of particularly difficult blends."
Answer: 35998.0

User story: "The ellipticity residuals from the HSC RC dataset processed in DM-10129 are much worse than the same dataset processed with the HSC stack.  This ticket is to discover the problem with the LSST version."
Answer: 43252.0

User story: "When you type DM-xxxx in chat, sqrbot should go turn that into a Jira link."
Answer: 8566.0

User story: "Either spawn a different container, or spawn a container with multiple kernels."
Answer: 27166.0

User story: "The sims_maps is missing an EUPS require for numpy. This is imported by {{tests/testFileSize.py}}. The fix is to add {{ setupRequired(numpy)}} to {{ups/sims_maps.table}}."
Answer: 10.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: Current behavior:  When there are more than one images displayed,  turning "WCS match" checkbox on will zoom and rotate all the images to the same pixel size and direction as the active image (selected, with orange color highlight), turning the checkbox off does nothing.     Improvement:  Turning off the "WCS match" should reset the images to a zero rotation.    Also include two bug fixes:    - A rotation issue: clicking rotate north on north up images fliped them south  - When north is up, clicking north up makes the image rotate south.    
Answer: 10167.0

User story: "As the weekly-release process can take some time (multiple retries, etc.), it has been decided it would be preferable to cut the tag at the end of the work week rather than at the beginning.  In order to keep the tag in sync with the calendar week, and not overwriting an existing tag, a one time > 7 day tag interval is required."
Answer: 5810.0

User story: "Install the limited test system (on loan from Dell pending full system acquisition).    *    Install computing chassis in racks  *    Prepare systems for network      "
Answer: 54448.0

User story: "Report lessons learned when creating the prototype, details, future work if to continue using DESDM framework to meet near term goals, etc"
Answer: 39099.0

User story: Near term goals are to save raw files into a custodial store and interact with the Batch Processing Service.       Try using DESDM framework that already has the concepts: file catalog, metadata table, file provenance, file transfers to/from compute jobs, etc.    Goal:   Save HSC raw files into a DESDM "home archive" along with enough metadata that can run pipeline steps inside the DESDM framework ([https://jira.lsstcorp.org/browse/DM-10468]).    A report will be tracked via a separate story.
Answer: 5.0

User story: "Get feedback on proposed policy, fold into policy document, and publish."
Answer: 50249.0

User story: "Based on review of existing policies, draft a proposed policy document."
Answer: 40392.0

User story: "Write up lessons learned, what would still need to be done to use DESDM framework to do a mid-scale production run in the near term, etc."
Answer: 37362.0

User story: "There are some changes in obs_subaru which are required for running pipe_analysis.  We want them on master to support QA efforts without the need to fuss with branches."
Answer: 24681.0

User story: See if can run a pipeline similar to the current HSC pipeline through an existing production workflow system in particular the DESDM framework.     Relies upon work done in data backbone file management prototyping ([https://jira.lsstcorp.org/browse/DM-9665])    As a proof of concept, it does not need to be production ready, but rather explore how command-line tasks could be used in a file-based, "hostile" executable framework.    (The write-up for this exploration will be listed as a separate story.)
Answer: 22.0

User story: "Refresh quotes given updated hardware list. Submit to project for final approval."
Answer: 57641.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 user input a position like (-34, 23) or (123, -91), Firefly treated it as object name and gave the error message "Could not resolve Object: Enter valid object". It is hard for user to understand exactly what was wrong with the input. In reality it is the position out of range error. Firefly should provide better error message for situation.    Another issue: "12.3, 23.4" is valid input, but "12.3, 23.4 gal" is not. And we have an example for the latter in the input pane.    input "18.0, -23.0"  has been interpreted into "18.0, -23.0  Equ J2000 ". but the latter is invalid    input "12 34 56.89 -23 45 16.56"  has been interpreted into 12h00m00.00s, -23d00m00.0s  Equ J2000
Answer: 492286.0

User story: Currently we have a new button "View Time Series: 3597607817453989" appear at the top if the table after search forced source. We could have this button appear after the object search.   But time series data is only available for i-band data. We need to add logic so the new button is clickable when an i-band Object row is selected, greyed-out when a row from a different band is selected, and provides a (long) tooltip that explains the point about forced photometry being limited to i-band Objects.    The same workflow should be implemented for AllWISE source data. From AllWISE source, the tool should get the associated  the forced sources  (in AllWISE multiepoch photometry table) and launch the Time series tool.
Answer: 60351.0

User story: "Adapt scatter plot and/or density plot to work within the design frame described in DM-9945.    This will be the start of plotting multiple 2D traces (series) within one chart space. "
Answer: 39098.0

User story: "There is a roundoff error for computing rotation for plots that are nearly north"
Answer: 167.0

User story: "Successfully restore a backed-up fileset. Use as baseline for timeline of recovery scenario. "
Answer: 142610.0

User story: "Work with camera personnel to facilitate installation of the simulation hardware."
Answer: 109106.0

User story: "Install the interface for the DAQ simulation hardware. "
Answer: 106462.0

User story: We get "mysql server has gone away" errors when dbserv hasn't been used in a while. This might not be a problem in the future, but it's a problem with pooled connections too.      The fix is to use pool_recycle parameter when creating sqlalchemy:    http://docs.sqlalchemy.org/en/latest/core/pooling.html    3600 seconds is probably appropriate.
Answer: 26406.0

User story: "Create (move) utility function to create a bbox from from an IRAF box from obs package to obs_base so others can use it."
Answer: 7318.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-9795 added a fix for a CModel prior bug, but left the fix deactivated pending verification on a larger amount of data.  Once verification is complete, activate the fix permanently.    Here's the code to activate the fix, from [~<USER>, and relevant for the {{CmdLineTask}} scripts or the multibandDriver:  {code}  def resetCModelWeights(cfg):      cfg.measurement.plugins["modelfit_CModel"].initial.weightsMultiplier = 1.      cfg.measurement.plugins["modelfit_CModel"].exp.weightsMultiplier = 1.0      cfg.measurement.plugins["modelfit_CModel"].dev.weightsMultiplier = 1.0    try:      resetCModelWeights(config)  except AttributeError:      resetCModelWeights(config.measureCoaddSources)      resetCModelWeights(config.forcedPhotCoadd)  {code}
Answer: 10363.0

User story: "The set of 3 general high-level functions is to support implementation of any VO service  methods, sync and async.  The functions would have the following signature templates:    global function template:      q_id = dax_plan(<named_op>, <args[]>) # return query id after checking the specified operation       j_id = dax_execute(q_id,  <opts[]>) # return job id for executing query       r = dax_fetch(j_id, <opts[]>) # get result for job id      a_array = dax_describe(id) # get metadata for any id      q_id: query id  j_id: job id  r : result   a_array: array of attributes pertaining to the id    On async vs sync mode:                  For sync request, dax_fetch() can be called immediately to fetch the result.                  For async request, status from dax_describe to provide info on current ETA          "
Answer: 161785.0

User story: "The first epoch of bad pixel masks in obs_subaru contains a bunch of bad columns that were dropped from subsequent epochs, but they are still relevant."
Answer: 1676.0

User story: "Adjust the line lengths to meet the new 79 character line length."
Answer: 542391.0

User story: "First FGCM command line task will retrieve source catalogs from the butler, call FGCM code to match stars, and store the output."
Answer: 51692.0

User story: "To use existing code in the stack for multi-band photometry, forced photometry, etc.. on the models generated with the DCR algorithm, many data types need to be added to obs_base. These will be added using the current name 'dcrModel' throughout, though it is expected that name might change following the eventual RFC to add the data type."
Answer: 8894.0

User story: Since the Regrid and LinearInterpolator are implemented, the number of grid lines can be chosen at users' disposal.  Thus, it will be more convenient for the users to be able to decide how many grid lines they want to see.  Also it will be more user friendly if they can turn on or off the labels.      Maybe allow the line to be at a round number position    It will be useful to add labels (on/off) and number of gridlines in the Layer's property dialog.  Currently, the Layer property dialog has "color" and "Delete" options.  It will be good to add two more options.
Answer: 736437.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: Store a set of HSC Bright Object Masks of version "Arcturus" to the {{/datasets/hsc}} butler root repo. These masks should become available as Butler type {{brightObjectMask}}    Also adding links for {{NB0816}} and {{NB0921}} filters for all tracts/patches.
Answer: 21808.0

User story: "SDSS PDAC Metadata needs a bit more cleaning and normalization in lsst/cat and lsst-dm/db_pdac_stripe82."
Answer: 435261.0

User story: "We need to setup user login page for PDAC. This is the first step in the authentication and authorization capabilities  implementation of the system. Pay attention to :  - collect user information  - get token after authentication  - pass token to DAX API  - "
Answer: 80505.0

User story: "Usually the application build date is at the bottom of the browser window on the dark bark. But when the browser window is small, the build date information flows up at the bottom of the visible portion of browser window.     We need to fix it. "
Answer: 49187.0

User story: "Provide a mechanism to show the coverage of dataset, e.g.  the SDSS Stripe 82 data, HSC processed data,  ...    DM-9350 described a procedure to make the region files for Stripe 82 images.    This will make better user experience in exploring the data.          "
Answer: 826919.0

User story: "SQR-019, written as a Jupyter notebook, demonstrates the functionality and usage patterns of the lsst.verify framework."
Answer: 33212.0

User story: "The idea of introducing SHA256 hashing in VO context is for the quick identification and verification of signatures for API method calls, as well as the returned content such as generated FITS images, which will become handy for caching and asynchronous operation."
Answer: 163240.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: "h1. Objectives    Deliverables of the task:   * an HTTP server built into the Replication Master Controller   * a REST API for monitoring and controlling the replication activities   * a prototype Web UI to test the services    h1. A summary of changes made in a context of this ticket    h2. Class replica/Application    The application base class  {code}replica/Application{code}  has been refactored and improved to derive from:  {code}std::enable_shared_from_this<Application>{code}  Also, improvements have been made to the command-line parser built into the above mentioned base class. Teh code of the Parser is located at:  {code}  replica/ApplicationTypes  {code}    h2. New master controller: replica/tools/qserv-replica-master-http    An improved version of the Master Replication Controller has been added. It has a built-in HTTP server based on Qserv module {code}qhttp{code}  Similarly to the previous version of the controller {code}replica/tools/qserv-replica-master{code} the new one also has two threads:  * Cluster Health Monitoring Thread  * The Linear Replication Loop Thread    The new controller can suspend/resume those threads. as well as launching new ones if needed.    h2. A new concept of the Control Thread has been introduced    Threads which now run within both flavors of the master controllers  {code}  replica/tools/qserv-replica-master  replica/tools/qserv-replica-master-http  {code}  have been made a subclasses in the following hierarchy:  * *replica/ControlThread*  ** *replica/HealthMonitorThread*  ** *replica/ReplicationThread*  ** *replica/DeleteWorkerThread*  ** *replica/HttpThread*    The vase class provides services and context for the derived threads. The threads also have states, which can be operated or inspected by calling the corresponding methods:  * *isRunning*  * *start*  * *stop*  * *startAndWait*    Fundamentally, these threads along with the previously mentioned class *Application* are the building blocks (an extension to the Replication Framework) allowing to build a family of various sophisticated  replication controllers.    h2. New reports added to the databases services API replica/DatabaseServices    These reports are used by the new REST API added into the Master Controller. here is a list of relevant classes which were modified in this context:  {code}  replica/DatabaseServices  replica/DatabaseServicesPool  replica/DatabaseServicesMySQL  {code}    h2. Extended API to the Configuration service    A method *allWorkers* added to the Configuration API to return a collection of names of all known workers regardless of their status. The following class was affected by this:  {code}  replica/Configuration  {code}    "
Answer: 846300.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: "Implementing the communication infrastructure (a distributed framework), added support for configuring the system. This includes the Controller (the interface for submitting and managing requests on the master side) and Worker servers (multi-threaded machinery for executing request in a context of a worker node). The initial configuration model is based on text files."
Answer: 226927.0

User story: "The details of the WISE catalogs loading into PDAC need to documented at:  * [https://confluence.lsstcorp.org/display/DM/Loading+catalogs+into+PDAC]"
Answer: 42877.0

User story: "Publish [LDM-294|https://github.com/lsst/LDM-294] to LSST the Docs, with a landing page pointing to PDFs. This landing page is an MVP that will be improved and made generally available for all LaTeX-based DM documents."
Answer: 12223.0

User story: "ghowl should ask for public_repo, not repo"
Answer: 1000.0

User story: "Provide programmatic access to UCD and VO Data Type item definitions.   JSON format chosen for its brevity, wide platform support, and popular usage in web environment. "
Answer: 43322.0

User story: "https://<host>/hub/home takes you back to the hub home where you can stop the server, or log out.  Add a button or a menu or something to the Lab UI to do that."
Answer: 10223.0

User story: "Run initial benchmark tests for the prototype alert distribution system to have some reference results for the NOAO brokers meeting."
Answer: 215955.0

User story: "As per RFC-308, we will remove the trailing {{repo}} from butler roots at NCSA.    The implementation of this ticket may be delayed at NCSA's pleasure.    This ticket is for the HSC repo /datasets/hsc/repo"
Answer: 1478146.0

User story: "Discuss implementation of Header client during  Integration Activity #3"
Answer: 159.0

User story: "Based on the steps/configs agreed in DM-9800, process the full set of the HSC PDR1 data. Monitor the execution progress and resolve non-stack issues (e.g. issues from bad execution). "
Answer: 56084.0

User story: "It has been requested that sqre temporarily disable jenkins CI builds on OSX due to the persistent disk space issues."
Answer: 30.0

User story: "Analyze and make summary plots for the metadata collected in DM-12440.  This may involve investigating further any failure modes that may have cropped up."
Answer: 429153.0

User story: "Once the validation datasets have been processed, analyze the outputs for completeness.  This will include categorizing the failure modes (if any exist :)).    Things to be collected could include:  1. Pass/Fail  2. Num ref/num source  3. Rms scatter and error on that value  4. Broad categories of failures  "
Answer: 88077.0

User story: "Run a large set of data through the stackified matcher.  These data should be run only once and with the configuration produced by the verification process (DM-9751)."
Answer: 84810.0

User story: "Need to fix a typo in a variable name."
Answer: 4.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: "Work performed in DM-10314, DM-10212 and DM-10042 has to be integrated on cc-IN2P3 nodes ccqserv100->124."
Answer: 28960.0

User story: "Work involved in SQR-018."
Answer: 90830.0

User story: "Persistent Storage for JupyterLab containers"
Answer: 7092.0

User story: "Create Python 3 - based JupyterLab LSST Stack"
Answer: 15408.0

User story: "Somehow in my many rebasings I lost the doxygen documentation to the Footprint constructors. Add that documentation back in."
Answer: 26884.0

User story: "Following the discussion on DM-9786, make a plan to restructure our code to reduce the size overhead introduced by the switch to pybind11.    This should lead to an RFCed proposal which leads to an update to the Developer Guide. The work doesn't have to be done on this ticket — we'll make more tickets for that, or (if the plan is ready in time) we'll do it as a hack session at LSST 2017."
Answer: 751388.0

User story: "In DM-10361, [~<USER> added a quick fix for a problem in this function which was breaking the stack demo.    That fix has done the trick, but it would have been nice to be able to catch the problem before it propagated as far as it did. There's already a fine unit test for this function; extend it to catch the problematic case."
Answer: 15941.0

User story: "Using a combination of daf_ingest and the pandas library, work on supporting table reading and writing in afw.table to arbitrary databases."
Answer: 152454.0

User story: "metaserv v1 work needs to be started to support more information about the catalogs loaded into it. This work should be informed by IVOA standards, specifically RegTap. "
Answer: 7545.0

User story: "The current PDAC tables in QServ do not have associated metadata with them. That metadata should be recovered, and add schema to lsst/cat project, as well as the schema in https://github.com/lsst-dm/db_pdac_stripe82."
Answer: 8296.0

User story: "Attend VO meeting in Shanghai and collaborate on Data Access Layer, Grid Web Services, and  Data Model working groups."
Answer: 50313.0

User story: "Moving some of the image processing to the client side allows us not to use as much memory on the server. We currently keep to versions of the FITS data a 2D array and a 1D array.  Remove the need to hold on to the 2D array."
Answer: 11576.0

User story: "Do the image processing to change color for the mask layers on the client side so that we do not have to call the server."
Answer: 1366.0

User story: "With the adoption of RFC-332 devtoolset-6 is to become the new baseline on both CentOS6 and CentOS7. This requires the CI build nodes to be upgraded to use devtoolset-6."
Answer: 326568.0

User story: "Investigate further into splitting KPM scripts to handle large query result scaling through either the python mysql library or mysql shell client. Collect lessons learned and methods on how to approach the solution for F17 tests."
Answer: 120845.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: "See, for example https://ci.lsst.codes/job/stack-os-matrix/label=centos-7,python=py2/23363/console: the result is clearly a failure (there's a huge list of warnings), but the log concludes:    {code}  *** Warning: output results not within error tolerance for:   The simple integration demo was successfully run.  ------------------------------------------------------------------------------    [PostBuildScript] - Execution post build scripts.  [PostBuildScript] Build is not failure : do not execute script  Archiving artifacts  Recording fingerprints  Finished: SUCCESS  {code}    It shouldn't."
Answer: 12807.0

User story: "This is to capture time spent on SuperTask meetings and documentation (reading) during April '17."
Answer: 48777.0

User story: "Following the merge of new {{Footprint}}​s, the stack demo is failing. See, for example, https://ci.lsst.codes/job/stack-os-matrix/label=centos-7,python=py2/23363/console.    Please fix it."
Answer: 1216.0

User story: "Statistics were generated at IN2P3 for correcting {{JOIN}} queries. The general process needs to be documented so we can optimize it in the future (see DM-9757 for reference)."
Answer: 59058.0

User story: "Given a single {{SourceRecord}} and the image it was produced from, create a new image corresponding to the state of the image when it was measured."
Answer: 123605.0

User story: "(1) There is a unused config {{brighterFatterKernelFile}} in the [IsrTask|https://github.com/lsst/ip_isr/blob/f7c21d50a0402556b168c16e3d71fed3bbd714ea/python/lsst/ip/isr/isrTask.py#L196].  It probably needs to be removed as Butler is used to retrieve the file now. Having a line like {{config.processCcd.isr.brighterFatterKernelFile=''}} in the config file is confusing while the brighter fatter kernel is read fine.    (2) The butler dataset type of the brighter fatter kernel file is inconsistent in [{{ip_isr}}|https://github.com/lsst/ip_isr/blob/f7c21d50a0402556b168c16e3d71fed3bbd714ea/python/lsst/ip/isr/isrTask.py#L342] and [{{obs_subaru}}|https://github.com/lsst/obs_subaru/blob/134c5dd63ab26e9b1bf03fc6cc280450c041df2a/python/lsst/obs/subaru/isr.py#L297]. {{ip_isr}} wants {{brighterFatterKernel}},  while {{obs_subaru}} and [obs_base|https://github.com/lsst/obs_base/blob/dd29b46197554e0a027fee66097c8a6c0dc34cd7/python/lsst/obs/base/cameraMapper.py#L676] want {{bfKernel}}.      It seems the brighter fatter correction has only been tested/used for subaru so far?     "
Answer: 783342.0

User story: "We want to use Jupyter notebooks to author verification reports. These reports will list what specifications passed or failed in a verification job.    This can be aided if we have a report class that can render as an HTML table in the notebook. As an MVP, astropy.table is ideal for this."
Answer: 42033.0

User story: "The HSC camera design paper has some relevant material on donuts. Read & understand it."
Answer: 39212.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: By the start of the F17 cycle, the NMF deblender should have matured to the level that it's of interest to the rest of the project. Give a "tech talk" to show it off.    (Preferably, do this before Jim has to give a talk on crowded fields in Lyon, so he can borrow some slides!)
Answer: 263624.0

User story: "Hopefully this will be the final beta release before hscPipe 5.0, which will be used for the next production run.  The following need to go in:    * DM-10315: Mask bad channels in ccd=33 (/)  * DM-10267: Port HSC support for PostgreSQL registries to LSST (/)  * DM-10430: Add time stamps to the standard outputs to BatchCmdLineTask (/)  * [-HSC-1423-|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1423]: Fix bright objects code (/)  * DM-10449: Restore bad pixel masks (/)  * DM-10451: Activate CModel prior fix (/)  * DM-10490: Cache camera in HscMapper (/)  * DM-10506: Run blendedness by default (/)  * DM-10504: Make more stringent cuts to input visits for HSC (/)  * DM-9918: Robustify sqlite use (/)  * DM-10546: meas.mosaic.updateExposure.applyMosaicResultsExposure will not if there is no mosaic solution (/)  * DM-10574: Hit AssertionError in deblender (/)  * DM-10598: Include pixels flags in forced measurement (/)  * DM-10621: ArgumentParser's butler doesn't output calibs in the calib storage (/)  * DM-10749: New filters for HSC (/)  * DM-10808: Add defect on ccd=43 (/)  * DM-10751: Fix module versions (/)  * DM-10835: Add color terms for NB filters (/)  * DM-10623: Mismatching dataId in logger output (/)  * DM-10930: Robustify tests/repository.py (/)"
Answer: 73743.0

User story: "In Firefly  chart column expression, we use log() as 10-based logarithm, ln() as natural logarithm.     I checked Python, Perl, C, C++, Java, the convention is to use log() as natural logarithm, and log10() as the 10-based logarithm.     We need to make the change and document it. "
Answer: 94784.0

User story: Mandeep S.S. Gill reports:    {quote}  have found what appears to be an error inside of:                                                     `afw/python/lsst/afw/display/ds9.py`, in current line 54:                                                                                                                                                   ```                self.exception = type(e)("%s (is display_d9 setup?)" % e)                          ```                                                                                                                                                                                                         which you can just see by sight needs correcting to: `display_ds9` in the parens.  {quote}    (ie, there is a missing "s").
Answer: 7.0

User story: "For backwards compatibility, we will want to be able to de-persist data processed with old stacks that have {{Calib}}s in them, and produce a PhotoCalib. We should be able to keep the old CalibFactory object and its registration and have it produce a PhotoCalib instead."
Answer: 947714.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 a search is long, we want to provide user with options to handle the situation: Cancel, background it.  When user chooses to put the search in background, the system should put it in the Background Monitor with its status updated periodically. "
Answer: 125207.0

User story: In HistogramOption, the numBins field used the validator: "Validate.intRange.bind(null, 1, 500, 'numBins')" to validate its value.  However, when the empty string is entered in to the  numBins, the validation still shows it is valid.  The empty string is not in the range of 1-500, by definition, it is not valid. 
Answer: 8948.0

User story: "Update both shared stacks on {{lsst-dev01}} to build against devtoolset-6.    Since this won't be ABI compatible with the earlier (no-devtoolset) stacks, we'll need to create entirely new stacks, which should probably build over a weekend."
Answer: 282346.0

User story: "Update the DM Developer Guide and all relevant packages (probably only {{sconsutils}}) to switch to C++14."
Answer: 331567.0

User story: "Inconsolata is needed to build the lsst-texmf examples, but it is not a default font on macOS. Including inconsolata in the lsst-texmf distribution would help our macOS users."
Answer: 52820.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: "Make Hub-spawning-Lab pods work with JL >= 0.20"
Answer: 31624.0

User story: "tickets/DM-10285 is part of this; so is displaying motd."
Answer: 4004.0

User story: "We need a service account for webserv on lsst10.    The standard privileges are fine for that account, but please also add the following grant:    {code}  GRANT SELECT ON `<USER>metaServ_core`.* TO 'webserv'@'%';  {code}"
Answer: 4.0

User story: "[~<USER> and I believe that the main failure of the current deblender is due to the difference between a sources peak position and its integer position in the pixel grid, which causes the symmetry operator to fail. In DM-10189 we created a translation operator that can shift the position of the peak to a fractional position and before we implement a solution to fit this position (DM-10310) it will be advantageous to check use the exact position (known in a simulated image) and see if this resolves the problem.    There is no reason to proceed with DM-10310 until we are sure that better positions and the translation operator will improve the deblender performance.    Since this ticket requires re-writing the functions that calculate the likelihood, this will also include updating the intensity matrix ({S}} in the NMF code) so that each source is in the center pixel. This suggestion by [~<USER> allows each source to use the same monotonicity and symmetry operators, whose calculation were one of the more time consuming parts of the new deblender. It should also make optimization easier once parts of the code are ported to C++."
Answer: 15775.0

User story: "Need to collect all configuration files, Dockefiles, kubernetes files and instructions to deploy jupyterhub with NFS mounted volume on Kubernetes"
Answer: 96477.0

User story: "Add another lsst sub group for jupyterhub users "
Answer: 10003.0

User story: "Describe (my) perception of the current state of the SuperTask interface from the Science Pipelines perspective to gather feedback from other Science Pipelines stakeholders and clarify any problems to the rest of the SuperTask working group."
Answer: 36055.0

User story: "[~<USER> would like to be able to use ipdb with the shared stack on lsst-dev.    Currently, {{pip install ipdb --user}} gives an {{IOError: [Errno 13] Permission denied: '/ssd/lsstsw/stack_20170409/Linux64/miniconda2/4.2.12.lsst2/lib/python2.7/site-packages/easy-install.pth'}} error.    This ticket is to either get that working, or install it for everyone, or just get ipdb included in the stack. The choice is yours! :)"
Answer: 1469.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 the snippet:  {code:python}      import os        dataPath = os.path.join(""/datasets"", ""hsc"", ""repo"", ""rerun"",                              ""private"", ""<USER>", ""RC"", ""DM-10084-mosaic"")        butler = dafPersist.Butler(dataPath)        dataId = dict(tract=8766, patch='2,1', filter='HSC-I')        coadd = butler.get(""deepCoadd_calexp"", dataId)        ci = coadd.getInfo().getCoaddInputs()        for ccd in ci.ccds:          fn = butler.get(""calexp_filename"", dataId, visit=ccd[""visit""], ccd=ccd[""ccd""])[0]          print ccd[""visit""], ccd[""ccd""], fn, os.path.exists(fn), butler.get(""calexp"", dataId, visit=ccd[""visit""], ccd=ccd[""ccd""]).getDimensions()          break  {code}  Returns:  {code}      7304 8 /datasets/hsc/repo/rerun/private/<USER>RC/DM-10084-mosaic/00995/HSC-I/corr/CORR-0007304-008.fits False (2048, 4176)  {code}    In the case of a {{get}} (where {{write=False}}) the Butler should not be returning a path to a file that does not exist, it should look in parent repositories until an existing file is found, or return something meaning ""file not found"".    This seems to be an issue related to how bypass functions work. I think it’s because there’s no consideration for {{write=True}} or {{False}} in the filename bypass function (as there normally is for `map`ping), and so the {{map_xyz_filename}} function returns the first location its able to map (which would be appropriate for a `put` where {{write=True}} but is not appropriate for a {{get}} where {{write=False}})."
Answer: 465052.0

User story: "Decommission VMs for S17 cycle, including:  * lsst-condor, lsst-launch, lsst8  * lsst-bast1, lsst-bat2  * lsst-buildx, lsst-eval  * original alert production simulator VMs"
Answer: 14739.0

User story: "Decommission physical hardware for S17 cycle, including:  * lsst-dev-old  * lsst-dbdev4 (to be replaced)  * lsst-suidev   "
Answer: 60557.0

User story: "Create plan for decommissioning LSST hardware during cycle S17. Include processes for:   * announcing decommissioning   * wiping hardware   * storage of spare hardware   * returning hardware and components to owners   * surplussing systems no longer usable   * updating inventory"
Answer: 14671.0

User story: "Furusawa-san writes:  {quote}  I found that some bias and dark frames for recent ccd=33 data failed  to create due to bad readout chennels. I propose to add a defect region  for two whole channels of ccd=33 in and after 2016-11 run for the next  production.  {quote}"
Answer: 2947.0

User story: "kubernetes and kubeadm version have been updagred, but it requires some changes in Qserv deployment scripts."
Answer: 1776.0