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: "As [~<USER> noted in DM-6463: {quote}for LSST sdss shape chooses a slightly different footprint. See computeAdaptiveMomentsBBox in SdssShape.cc.{quote}  Bob recalls seeing some effects due to this change, and the [commit message|https://github.com/lsst/meas_base/commit/2e479a4e6e74afa66832aa05680a6e89cc02af1a] of the changeset (made on the LSST stack but not on the HSC stack) states: {quote}*Rewrite set_amom_bbox using afw::geom operators*  This changes results slightly in lsst_dm_stack_demo (as the the region of  pixels used in the fit can differ by 1 pixel due to different rounding).{quote}    This ticket is to more deeply investigate the effects of this change and, in particular, see if it contributes to differences seen between the stacks: e.g. the increasing with magnitude offset of the SDSS trace radii:    !compareVisit-v30490-trace_-psfMagHist.png|width=500!    Of note, the difference does not show up in a comparison of the psf model trace radii:  !compareVisit-v30490-psfTrace_-psfMagHist.png|width=500!"
Answer: 11718.0

User story: Blue Ocean is currently in beta and is nearing a stable release.  Moving the production instance to BO would require removal of any "matrix" job types as they are incompatible with the new UI.
Answer: 295209.0

User story: "Jenkins LTS 2.32.2 has been released which includes fixes for a number of security issues that are present in 2.19.4 (current production release) https://jenkins.io/security/advisory/2017-02-01/    We were unable to upgrade past 2.19.4 due to the swarm plugin not being forward compatible.  However, a new release of the swarm plugin (3.3) was made last Friday, that should be compatible with the current LTS release.    Updating the swarm client made resolve/improve the the segv's in DM-8915."
Answer: 273754.0

User story: "Attend LSST DESC collaboration meeting at SLAC.  Report on DM work for Photometric Corrections working group, especially regarding calibration workshop at Harvard.  Discuss survey completeness quantification and related issues."
Answer: 13426.0

User story: "The default argument for the bitmask in {{afw::detection::Footprint::intersectMask}} does not work with the pybind11 wrapper. Investigate why and fix."
Answer: 1816637.0

User story: "Create an obs package that provides basic access to data from test stand 3 (ie, individual CCDs). This should include loading the data from disk and providing all the standard LSST functionality, but does not need to integrate with Camera Team systems (e.g. you don't need to ingest metadata directly from eTraveller, or similar)."
Answer: 51002.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: "If i use an external viewer to show the histogram (API/HTML static page), i was expecting be able to click on 'Charts' drop-drown button and make another histogram or scatter plot.  It's not possible. Is fine for now but once i clicked, there is no way i can go back to the histogram displayed previously.  We should fix that part adding at least a 'go back' button. What do you think?    Go to demo page:    http://localhost:8080/firefly/demo/ffapi-highlevel-test.html    and click on 'show histogram'. A viewer will open a new tab. Click then on the 'Charts' to see the flow described above."
Answer: 90642.0

User story: "This package is in active use and should benefit from regular CI. Adding it to lsst_distrib will require an RFC."
Answer: 15335.0

User story: "The old example of using these tasks will likely be removed following DM-9142 & RFC-290. When an appropriate test harness is available to ensure it actually works, re-instate it."
Answer: 1820468.0

User story: "The old {{IsrTask}} example will likely be removed following DM-9197 & RFC-290. When an appropriate test harness is available to ensure it actually works, re-instate it."
Answer: 1820470.0

User story: We occasionally observe a "wave" of github fetch/clone failures from {{lsstsw / lsst_build}} in the jenkins env. Where a wave is several random failures over the course of a day or two and then there are no failures for weeks.  I am convinced that these are on the github end as I have experienced clone failures when running {{lsstsw}} outside the the jenkins env.    I am loath to retry the entire jenkins build upon any failure as this might result in a legitimate build failure unnecessarily tying up build slaves.  There are two  solutions that occur to me:    1) propagate errors up from {{lsst_build}} in such a way that the CI driver can determine the reason of failure and retry a set of failure modes    2) add git fetch/clone retrying support into {{lsst_build}}    I am leaning towards #2 as the implementation is straight forward and contained within a single component.
Answer: 538454.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: "For certain diagnostics plots, it is useful to select on specific subsets of the data.  An example subset would be the objects that were used actually in the PSF modeling, i.e. those with flag *calib_psfUsed=True*.  When plotting this subset for the coadds of the LSST stack processing of the HSC RC dataset (DM-6816), a large number of patches have no objects for which this flag is set.  While the list is not expected to be identical to the list from the visit processing (the flag is propagated based on the fraction of visits overlapping that object and contributing to the coadd that had the flag set for said object), ending up with a list of zero objects used for PSF modeling should be very unlikely.  The pattern is quite delineated, with sharp truncation lines beyond which no objects used in PSF modeling are found:    !plot-t0-HSC-I-footNpix_calib_psfUsed-sky-stars_LSST.png|width=500!    Of note, this does not happen for the same dataset processed through the HSC 4.0.5 stack (DM-9028):    !plot-t0-HSC-I-footNpix_calib_psfUsed-sky-stars_HSC.png|width=500!"
Answer: 70522.0

User story: "fix Phase folded table created  for time series viewer (DM-8670)   - fix the time column value (mjd) on the expanded cycle part. (the phase folded table is made to contain the data rows for two phase cycles): the value of 'mjd' column in the expanded part is duplicated from the original raw table.   - make the creation of phase folded to be derived from full set of raw table, not just partial raw table shown on the page.    "
Answer: 7689.0

User story: Highlighting objects based on a "third" parameter, e.g. a flag setting, (other than spatial, for which we are already producing diagnostic figures) can be very useful in diagnosing pathologies (see, e.g. DM-9252).  This ticket is to add this ability to the analysis plotting scripts.
Answer: 74910.0

User story: "Add a cron job that will automatically run the shared-stack script on Perseus to install new weeklies."
Answer: 4226.0

User story: "This work removes:  {code}  ctrl_events  {code}  from {{etc/repos.yaml}}    and moves the repo to  {code}  lsst-dm/legacy_ctrl_events  {code}"
Answer: 10565.0

User story: "We use ctrl_events to interact with ctrl_orca once workflows start.   I'll be replacing that functionality with a REST API interface, and moving ctrl_events."
Answer: 10543.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. Goals    This task complements an effort for loading *object* and *forced source* catalogs into PDAC (as per JIRA [DM-9372]). The goal is to load the complementary image metadata tables. Note that these are *non-partitioned* tables which would need to be fully replicated across all _worker_ nodes of the *Qserv* cluster in *PDAC*.    h1. References    Properties of the dataset are documented at:  * [https://confluence.lsstcorp.org/display/DM/Properties+of+the+WISE+and+NEOWISE+mission+data]    A list of WISE catalogs to be loaded:  * [https://confluence.lsstcorp.org/display/DM/PDAC+v2]     Tools and scripts developed for this efforts are found at the GitHub package:  * [https://github.com/lsst-dm/db_pdac_wise]  "
Answer: 132152.0

User story: "h1. Goals    Download from IPAC, pre-reprocess (if needed), partition and load into PDAC *object* and *forced source* catalogs of various *WISE* missions.    h1. References    Properties of the dataset are documented at:  * [https://confluence.lsstcorp.org/display/DM/Properties+of+the+WISE+and+NEOWISE+mission+data]    A list of WISE catalogs to be loaded:  * [https://confluence.lsstcorp.org/display/DM/PDAC+v2]     Tools and scripts developed for this efforts are found at the GitHub package:  * [https://github.com/lsst-dm/db_pdac_wise]    "
Answer: 158348.0

User story: "We need to provide option to display the image cutout, using DAX API."
Answer: 29920.0

User story: "We have found pickling support more reliable using {{\_\_reduce\_\_}} than {{\_\_getstate\_\_}}/{{\_\_setstate\_\_}}. There are still eight instances of the latter that should be changed, one each in {{dateTime.cc}} and {{propertyList.cc}} and various in python files."
Answer: 1892857.0

User story: "Using the framework and content provided in DM-9317, update the the content as need for PDAC purpose. "
Answer: 951818.0

User story: "While I was working on the unit test for this class, I found that the CentralPoint class did not use the Elzinga-Hearn Algorithm as described at the beginning of the class. There are no further document about the algorithm."
Answer: 1722425.0

User story: "My ELK system has had instances have their root file systems become read-only.    This needs to be reported to NCSA and work arounds need to be found.  "
Answer: 1456.0

User story: "[~<USER> has prototyped a system for reducing data from the Calibration Telescope. Integrate this with the LSST stack, so that it ingests data using obs_ctio0m9 & manipulates data using standard LSST primitives."
Answer: 170953.0

User story: Data from the 0.9m telescope at CTIO is being used to prototype the processing pipeline for the Calibration Telescope. In order to ingest it into the stack, we'll need an appropriate obs package ("obs_ctio0m9"). Please create one.
Answer: 115190.0

User story: "The git-lfs legacy API logic in lsst-build which sets {{batch = false}} in the git configuration should be removed. The new git-lfs client (2.0+) will not support this API.  "
Answer: 10136.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: "Based on the input provided by [~<USER> in DM-9356, update LDM-151 to provide a complete description of the plans for processing data from the Calibration Telescope."
Answer: 123575.0

User story: "Let's find a guinea pig, eg [~<USER> or [~<USER> or [~<USER> or... whoever sticks their head up in if we ask in #dm"
Answer: 1559.0

User story: "Currently pybind11 defaults to {{py::return_value_policy::copy}} or ({{py::return_value_policy::take_ownership}}) for (const) references (and pointers) respectively.  It would be better if it would require an explicit {{return_value_policy}} to be specified instead.    Investigate this further and potentially push changes upstream."
Answer: 1893069.0

User story: "Summarize the plans for processing data from the Calibration Telescope and any open questions that remain about the approach to be taken in bullet-point form. Provide them to [~<USER> for incorporation into LDM-151."
Answer: 123751.0

User story: "Create a test ELK cluster for Adam."
Answer: 48861.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-9186 changed how the ISR configuration is set, but the configuration for calib construction wasn't updated to match."
Answer: 1379.0

User story: "This is the second part of changes to support LSST time series, which should handle band selection in UI.    We need to support mission specific input, from which the x and y columns and automatic filtering of the raw table depending on the input parameters (band selection).    https://github.com/Caltech-IPAC/firefly/pull/313    Attached to this ticket, please find the sample LSST multi-band table for object id 2990683841366709."
Answer: 21299.0

User story: The following change will be in Firefly:  * histogram  Y axis label: Number  * Charts scatter/histogram option dialog, "search" button:  "OK"  * Choose columns dialog "Set column or expression" button:  "OK"    The following changes will be in IRSA Viewer:  
Answer: 8430.0

User story: "In the current LDM-151 {{draft}} branch,  {{DiffExp}} is used for difference images in the AP sections, but {{DIAExp}} is used in the DRP sections."
Answer: 23268.0

User story: "For uniform binning (fixed bin size), there are two different ways to give the input:  1. number of bins (the current option only)  OR  2. bin width    Label may needs to be changed as well.    [March-2-2017]  To have a choice of the number of bins or bin width, two radio buttons and one text box are added.  By default, the number of bins is selected.  When the radio button is selected, a new value either number of bins or bin width should be entered and validated.   Then the histogram will be updated accordingly. Since no data range information is available before sending the request, the bin width can not be validated correction.  Thus, an exception is thrown if the bin width is large than the data range.     [March-16-17]  Based on the modified requirements, the UI is  # Add two radio buttons and two input text boxes next to the two radio buttons, one of which is number of bins and the other is bin width.  #  Add two input text boxes below the two set radio/text boxes.  One of which is for min and the other is max    After several discussions and iterations, we added the following:  # For single column histogram, since the data min/max is stored in the column variable array, they can be used to pre-fill the min and max.  # The bin width is calculated based on the number of bins and min and max and then the bin width is pre-filled.  # The bin width is recalculated each time when number of bins or min or max changes.  # When number of bin is selected, the bin width text box is disabled, when the bin width is selected, number of bins text box is disabled    "
Answer: 51590.0

User story: As user types in the input input, the list of suggestions appear. The unit should be in parenthesis "()", not after the comma ","    For scatter/line/histogram charts.
Answer: 8488.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: "Symbol choice dialog:  * size of the symbol is between 3-20 pixels, lets change it to 3-100. display the unit  * add ? for help, take the description away  * use radio button, not checkbox  "
Answer: 8503.0

User story: "The radio button choices should be above the polygon input box.  Labels for radio buttons change: Search area: image, visible,custom  "
Answer: 2928.0

User story: "{{PhotoCalTask}} currently inherits from {{lsst.meas.algorithms.RefMatchTask}}, which defaults to using the {{MatchOptimisticBTask}} for matching.  The {{MatchOptimisticBTask}} is a full-featured matcher allowing for offsets and rotations, but by the time photometric calibration is required we are expected to have done all astrometric calibration and the use of a full-featured matcher is inviting trouble and requires unnecessary duplication of configuration changes (i.e., any configuration changes need to be mirrored from {{calibrate.astrometry.matcher}} to {{calibrate.photoCal.matcher}}).    I suggest changing the {{PhotoCalTask}} to use the {{DirectMatchTask}}, in which case the inheritance from {{RefMatchTask}} could be removed, greatly simplifying the design."
Answer: 492389.0

User story: "LCR-836 (already created) is for a long-pending typographic correction to LSE-69 to get it to match LSE-130's section headings.    The work on this ticket is to prepare the new docgen and submit it to the CCB. "
Answer: 1485351.0

User story: "obs_monocam provides a [{{monocamIngestImages.py}}|https://github.com/lsst/obs_monocam/blob/786219475ffd0e022c98234d5b00a5c30ca668c5/bin.src/monocamIngestImages.py] which attempts to import {{lsst.obs.monocam.ingest.MonocamIngestTask}}. {{MonocamIngestTask}} [was removed in {{7862194}}|https://github.com/lsst/obs_monocam/commit/786219475ffd0e022c98234d5b00a5c30ca668c5#diff-16d2f190c33eaa0d3ef05279458bd775L95]. I conclude that {{monocamIngestImages.py}} is a confusing remnant which should be removed."
Answer: 1451814.0

User story: "We want to have a generic reverse proxy set up for all web services using an nginx container.  This will allow us two things:  1. The ability to decouple imgserv, dbserv, metaserv, and future *servs  2. The ability to potentially scale requests in a round-robin fashion to multiple machines, if necessary, thanks to REST semantics.    The decoupling of imgserv, dbserv, and metaserv will be performed in a different story"
Answer: 1793674.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 issue was raised by [~<USER> during the code review of DM-9034 and led to this ticket.    {code:java}             if vdrp_measurement_doc['value'] is None:               continue  +        if vdrp_measurement_doc['metric']['name'] not in registered_metrics:  +            metrics.append(shim_metric_definition(vdrp_measurement_doc))         {code}    @<USER>  Is it possible for a metric to appear multiple times in this list? Like, if there's multiple AM1 measurements in different bands, or multiple measurements against different specifications of a metric, then couldn't we have duplicates here?    @<USER>  That's a good point. In this implementation the metric name is unique so if there is already an AM1 registered it would not pick another AM1 with a different specification.    I see the problem when a metric, say AD1, depends on another metric specification, in this case AF1. We end up with three measurements of AD1 for each AF1 specification level, right?    I think if a metric has a different parameter or specification it should be named differently, so that we can identify each metric uniquely by its name, or perhaps have another mechanism like a composite primary key based on the metric name and specification? we should think on how to display the metric measurements in this situation too."
Answer: 1040057.0

User story: "We could add support for parallel execution a la CmdLineTask to current command line activator. This is not at all final solution but could already help  for some use cases (e.g. validateDrpTask)"
Answer: 19593.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: "Need a Time Series viewer app for IRSA, under IFE repository.    Please, create app with no logo (for now - for later probably we will need a new icon).    "
Answer: 19769.0

User story: "Please, to be consistent with the new name of Time Series viewer:    - Rename {{lc.html}} to {{ts.html}} (Time Series replace Light-Curve)  - {{wise}} should be upper case    Thanks."
Answer: 2955.0

User story: "We now have a shared stack installed on Tiger, and one on Perseus, with marginally different setup instructions due to the different operating systems available on those clusters. We also have a variety of HSC stacks.    It's pretty confusing to figure out what initialization in terms of loading devtoolsets, sourcing files, etc is needed to use each one. Please write a short document which describes how it all works, and make it available somewhere obvious."
Answer: 91891.0

User story: "The result table needs additional columns to indicate which job and re-try they are associated with so those rows can be stripped if that job-retry is cancelled."
Answer: 345546.0

User story: "Call SetCBThreads to increase maximum number of threads. Call must be made before calling getservice.     Use PRD_Hold in ProcessResponseData calls to keep responses to jobs from preventing new jobs from being sent to workers."
Answer: 40310.0

User story: "Benchmark and fine-tune CEPH on Openstack (Galactica platform) for a few worker nodes.    Useful links:  - http://www.thegeekstuff.com/2011/05/iozone-examples/  - http://iozone.org/    And also send xrootd worker logs related to Source full-scan query cancellation on Galactica to Andy H."
Answer: 92767.0

User story: "Use xrootd's affinity feature to consistently choose the same node for chunks on shared scans."
Answer: 1545558.0

User story: "Make a microservice send logs to ELK stack."
Answer: 24275.0

User story: "Migrate Firefly's onlinehelp system so that it can be used by SUIT.  - created github repository: https://github.com/lsst/suit-onlinehelp/  - copy content from existing irsaviewer online help.  - change build/config script for SUIT.  - setup build/install environment for pdac    To build and install online help on pdac:  - log into sui-tomcat01  - switch to suiadmin  - source /hydra/cm/env/env.sh  - cd /hydra/cm/suit-onlinehelp  - git pull  - gradle install"
Answer: 20369.0

User story: meas_base's {{tests/testVariance.py}} contains the line:    {code}  var.getArray()[bad, :] = float("nan")  {code}    Where {{bad}} is {{54.0}}.    [As of NumPy 1.12|https://docs.scipy.org/doc/numpy/release.html#deprecationwarning-to-error], this will throw an {{IndexError}} and the tests (obviously) fail.    Should be an easy fix.
Answer: 2941.0

User story: "The new flask is not building on master and this is causing the weekly tag/release build to fail. It looks like this is being triggered by DM-9268."
Answer: 2853.0

User story: "Put together a draft plan including rough dates, functionality, products, other information as necessary for discussions and planning."
Answer: 83626.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: "Reworking LDM-144 tape & tape requirements tabs for initial feedback on redesign."
Answer: 83626.0

User story: "Following discussion on Slack the other day, it probably makes sense to get every DRP team member who currently has a Tiger account an account on Perseus."
Answer: 4707.0

User story: "[~<USER> has provided me with some code he's been experimenting with to explore interfaces to the Science Pipelines and has asked for feedback. Provide it to him (or find somebody else who can).    He writes:    {quote}  Thanks, this would be very helpful! I’ve pushed the current working version to https://github.com/stargaser/forced_phot . The goal is return a table of photometry at a specified location on a specified  set of single-epoch exposures.    The README has some information. The main script is “get_forcedphot.py” and the arguments are:  ------------------  usage: get_forcedphot.py [-h]                           input_repo output_repo json_input coord_str                           filter_name output_table    Run forced photometry on specified images and output a time-series table    positional arguments:    input_repo    input repository directory path for images    output_repo   dummy repository directory for schema    json_input    json file as returned by imgserv    coord_str     coordinates string as name,ra,dec    filter_name   name of filter to subset input table [ugriz]    output_table  output table path in FITS format    optional arguments:    -h, --help    show this help message and exit  ———————    To interface with Firefly, this will be modified to take a JSON input from Firefly and to return a JSON file specifying the output table location.    Some problems I had include:  * couldn’t get the schema right to add PSF magnitudes  * couldn’t use the writeOutput method for each catalog because of schema problem  * calib.getMagnitudes couldn’t convert the ndarrays for psfFlux to C++ (non-aligned arrays?)  * multiple exposures can be specified with multiple ‘—id ‘ arguments — very cool! Is there a way to gather up all the individual results into one table in the same pipeline task?    To get something working, I have fallen back to Astropy to manipulate the catalog table files.    For now, I’ve been running this on lsst-dev since the data are available there, in /home/<USER>projects/forced_phot.  {quote}"
Answer: 10010.0

User story: "We'll use the {{perseus.princeton.edu}} cluster for processing HSC data through the stack until the public data release can be transferred to NCSA because it's less overloaded than Tiger. Install the LSST stack there."
Answer: 583.0

User story: "Next step in understanding alert production performance is to see if paralellising processing can help with reducing database access overhead."
Answer: 22432.0

User story: "Implement and deploy an Ansible role to use filebeat to forward nginx access and error logs to Panopticon."
Answer: 164150.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 function {{afw::image::makeWcs(metadata, stripMetadata}} with its second argument true does not strip metadata if certain values are present because those values induce a deep copy of the metadata, and the keywords are stripped from the copy.  "
Answer: 1171.0

User story: "At the DMLT face-to-face meeting in January 2017 it was decided that the SUI and QA sections should be removed from LDM-151. Both these sections are being handled in other documents."
Answer: 128553.0

User story: "We still have a problem where important documents are found on the old LSST Trac system (https://dev.lsstcorp.org/trac/) that should be moved to confluence or tech notes, and where there are bug reports and work tickets that have not migrated to JIRA.    At Bremerton All Hands we made a first pass of analyzing the open JIRA tickets to decide which ones should be migrated but that work was never followed up on and the migration has not occurred. This topic also was discussed at the documentation meeting last September.    Either someone should lead this effort or we should officially state that we have no intention of analyzing the Trac system and will keep it around for as long as possible and not deprecate it.    Can DMLT (or DM Lead) please make a decision on how to proceed.    Some tickets have been moved over but it's not always obvious from the Trac side that a ticket has been migrated.    "
Answer: 1623248.0

User story: "Function {{makeAmp}} in {{makeCamera.py}} has two undefined variables: {{nExtended}} and {{nOverclock}}."
Answer: 1809325.0

User story: "The validate_drp processing of {{validation_data_hsc}} outputs results for multiple filters.  Multiple changes are needed in order to support one than one filter per dataset run.    * The squash data model needs to be modified to add the concept of a filter.  Be it either a one-many relationship of run to filter(s) or each filter is handled a separate run with the same {{id}}.  * Filter selection widget for the dashboard plots"
Answer: 819545.0

User story: "I have completed the updates to the documentation for https://github.com/lsst/sims_survey_fields that allow it to build locally with the current local build system. Now we should be able to get it into LSST the Docs. Please let me know if there are things I can do to help with the work. "
Answer: 1886665.0

User story: "LDM-151 currently includes a report entitled _Measurement of Blended Objects in LSST_ by [~<USER>. This report is anomalous in that directory and is cited directly by LDM-151. It should be relocated to a standalone repository as a tech note."
Answer: 65018.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: "Three tickets: RFC-267, RFC-268 and RFC-269 seem to be duplicates of RFC-270. I don't quite understand how we have 4 identical tickets from [~<USER>.    * 267: was created 04/Jan/17 1:36 PM  * 268: 04/Jan/17 1:38 PM  * 269: 04/Jan/17 1:47 PM  * 270: 04/Jan/17 1:52 PM    Maybe they were drafts. The problem though is that I can not delete the 3 spurious RFCs as they do not have any workflow buttons for me to click on. RFC-270 does have the workflow buttons.    Please delete the 3 spurious RFCs. Weirdly, they were not visible to me last week when I was analyzing Proposed RFCs so I'm not sure why they appeared over this weekend."
Answer: 1801.0

User story: If I am viewing an RFC and I click on the link "Request for Comments" at the top which seemingly should take me to the root RFC page at https://jira.lsstcorp.org/browse/RFC, I in fact end up at a NCSA kanban board: https://jira.lsstcorp.org/secure/RapidBoard.jspa?rapidView=119&projectKey=RFC    Can you please fix it so I can see RFC status instead?
Answer: 1875.0

User story: "Microservices currently use standalone flask.  We want to move them to uwsgi."
Answer: 46383.0

User story: "New flexible parameter description, to be used in updated chi^2 module."
Answer: 95036.0

User story: "Implement a script to do forced photometry that can be used as a server-side extension to Firefly, on the sui-tomcat* machines used in PDAC v1.    * Install necessary version of LSST stack  * Implement a forced photometry procedure using the stack  "
Answer: 76159.0

User story: "Port the obs_monocam package to pybind11    Note that obs_monocam is part of lsst_distrib"
Answer: 1.0

User story: "Jonathon Sick has a boiler plate to bild docs for Numpy doc docstring.   This is a ticket to use that for SUIT Python doc build.  https://community.lsst.org/t/what-packages-have-numpydoc-docstrings-so-far/1612      Please add the cheat sheet for Python doc generation in https://confluence.lsstcorp.org/display/DM/Python+document+generation+cheat+sheet.    "
Answer: 68752.0

User story: "So far, couple of minor clean-up need to happen to prepare a RC for IRSA (IFE):    - Remove logo (DM-9327)    This ticket will be updated with more feedback later.  "
Answer: 25656.0

User story: "Some RFCs contain sensitive information (in the description or commentary) that should not be publicly accessible. Please make it possible to lock down specific RFC tickets."
Answer: 1587351.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: "Refinement of costing and schedule with DM and overall project.    * Reorganization of the ITC component of the proposed WBS according to operational enclaves.  * Verification of the completeness of the proposed 2000-line WBS with NCSA IT groups. Added ITC elements needed by network-based security for processing intrusion detection logs.  * Minor additions to the WBS based on steering group discussions with technical areas of the LSST project at NCSA. Example is header metadata client for writing and storing headers in the EFD and construction of simulators needed for raft-scale and full-scale Level 1 test stands.  * Began investigating value engineering opportunities."
Answer: 40025.0

User story: "Refinement of plan, facility visits, updates to budget etc., needed to complete the LSST operations plan, which is a deliverable of the LSST MREFC. Develop use cases describing operational processes between departments as recommended by the review committee. Review ops plan and labor and non-labor estimates and identify changes that need to be made to complete the LSST operations plan.    * Deep dive into content and structure of sizing model to model file handling and file volume for data retention investigation. Creating schema to manage input data and a separate analysis environment.  * Meetings with CC-IN2P3 to discuss plans for coordinated operations, including data movement between sites and a role in disaster recovery.  * Meetings with FNAL computing division representatives to explore interest in participation of DPP operations, including IT systems, database administration, storage and file system services, and networking.  * Verify FTEs needed to support north-south networking in DPP operations."
Answer: 40063.0

User story: "The OCS Bridge DM subscribe code is being refactored and the test needs updating."
Answer: 178655.0

User story: "Adequate testing of the DMCS component requires a message broker instrument be running. The test module for this task brings together the message send code, and then checks the responses."
Answer: 1.0

User story: "December Demo code for OCS Bridge used C++ to send messages to the DMCS, and Python w/Boost to receive. It was the intention of the OCS Bridge design to make it a completely C++ entity, and this story tracks the effort to do so."
Answer: 34659.0

User story: "Update all git-lfs repositories to be compliant with current git-lfs best practices.    1. Remove {{batch = false}} configurations.  2. Ensure {{.lfsconfig}} files exist."
Answer: 14977.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: "Using {{py::module::import}} on a nonexistent module raises {{py::error_already_set}} with an import error, which I saw propagate out to {{terminate}} despite being thrown within a try block defined by the PYBIND11_PLUGIN macro.  The situation must be more complex than it seems, but compiler optimization is getting in the way of my ability to debug and I don't want to recompile afw without optimization now anyway.  Further investigation should probably be done on a minimal test case anyway so we can easily report it upstream if it is a bug."
Answer: 118201.0

User story: "Add the new hsc dataset / driver script (DM-6328) to the jenkins {{validate_drp}} job."
Answer: 34946.0

User story: "Currently `scripts.pybind11` prepends an underscore to the source file base name to create the name of the generated module. This ticket aims to modify the script to only prepend the underscore if one is not already present in the source file name. This will allow seamless transition to the new convention from RFC-281."
Answer: 73.0

User story: "Moving back to the LSST VM Cluster is not trivial. It is terrific for testing up to 11 forwarder and distributor pairings, bit when it was first used for the testing of prompt processing, it was functional but crude in that it did not have the more sophisticated configuration capabilities recently added to the base part of the system. Now development efforts on Nebula have been terminated except for a small, turnkey demo configured for archiving with one forwarder.    The VM Cluster components had to be reassigned, the proper software installed via git and scripts on all 40 nodes, and outside software reinstalled/updated. This story tracks the effort."
Answer: 2.0

User story: {{key}} appears to have been removed from the API for {{Butler.queryMetadata}}, but it appears in the doc and implementation:    {code}      def queryMetadata(self, datasetType, format=None, dataId={}, **rest):          """Returns the valid values for one or more keys when given a partial          input collection data id.            Parameters          ----------          datasetType - str              The type of dataset to inquire about.          key - str              A key giving the level of granularity of the inquiry.          format - str, tuple              An optional key or tuple of keys to be returned.          dataId - DataId, dict              The partial data id.          **rest -              Keyword arguments for the partial data id.            Returns          -------          A list of valid values or tuples of valid values as specified by the format (defaulting to the same as          the key) at the key's level of granularity.          """  ...          if format is None:              format = (key,)          else:              format = sequencify(format)  ...  {code}
Answer: 184.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 story is to collect the ticket and track them in order to prepare and release Time Series viewer (old LC) in March.    Links to issues should be added.    The RC is expected to happen around mid February. "
Answer: 62031.0

User story: The distribution of footprint sizes for "stars", here limited to those actually used in the PSF modeling, displays a bimodal distribution (two separate/offset sequences of declining nPix vs. mag):    !plot-v1228-footNpix_calib_psfUsed-psfMagHist.png|width=500!    Investigate the source of this behavior.
Answer: 28460.0

User story: "As discovered by DM-6561, the FlagHandler mechanism for connecting the enumeration of flags in C++ and the order in which the flags appear in the schema and internal FlagHandler structures is not robust.  Fix this, problem, so that the identifier used identify a particular flag and the lookup of the Flag Key are guaranteed to match.    Then fix the flagDecorator (it will be simpler) and all of the algorithms to match the new FlagHandler scheme."
Answer: 45397.0

User story: "In LSST catalog and image search, we need the feature, All Sky, to allow user to input query requirement(s) without giving a target.     This ticket is for the client side change."
Answer: 11779.0

User story: In LSST catalog and image search, we need the feature, All Sky, to allow user to input query requirement(s) without giving a target.  Need to implement the search processor(s) to support this.    The following items will be added to implement this request:    [LZ Feb-9-2017]  #  Add a  test to see if the search method is "allSky"  In the getSearchMethodCatalog method  # Add the same test  if the search type is "allSky" in the getMethodOnSearchTyp method  # Add the code to guard the user error when click search without any constraints in all sky search.  When such case happens, it will throw an EndUserException with error message.  
Answer: 16166.0

User story: "The automated RDS snapshots are a pain to restore and can't be downloaded out of AWS.  In addition to the automated RDS snapshots, we should be making periodic raw SQL dumps for backup, DR, and use in pre-deployment migration testing."
Answer: 8903.0

User story: "Yarn is a new package manager for JS.  It increases performance and is more reliable.    You do need to install yarn. From your command prompt:  npm install yarn -g  Depending on where you install node, you may need sudo for this to work.  I've updated our docs to reflect this new requirement.    In order to get consistent installs across machines, yarn.lock is used.  If you updated package.json, you need to run yarn install to create a new yarn.lock file.  You must commit the new yarn.lock file with your updated package.json for build to work."
Answer: 1693.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: "DMS-REQ-0131 says  {quote}  Calibration images shall be available for nightly observing in the DMS image archive at least 1 hour prior to the start of observing.  {quote}  This is impossible to verify without an understanding of when calibration data acquisition ends. I think there needs to be added clarification as to when calibration image acquisition ends and how much data will be taken during the day. Does calibration acquisition end 2 hours before the start of observing? Or 61 minutes prior? Are we observing continuously from dawn until that time?"
Answer: 37588.0

User story: "KPM timeseries plot points are ~8 ahead of US/Pacific and ~16 ahead of UTC.    See the attached screenshot of the dashboard vs. the corresponding qadb record    {code:java}  MariaDB [qadb]> select date from dashboard_job order by date desc limit 1;  +----------------------------+  | date                       |  +----------------------------+  | 2017-02-02 16:39:33.826112 |  +----------------------------+  1 row in set (0.00 sec)  {code}    My hunch is that bokeh is assuming that data is in the local TZ and doing a -> conversion by default.    "
Answer: 796640.0

User story: "At present, the KPM time series plots do not label the time axis with the timezone."
Answer: 393462.0

User story: "Revise the PDF handed out to new LSST hires starting at Princeton to reflect current reality."
Answer: 331.0

User story: "DM-9136 is editing LDM-151 to reflect requirements from the beam projector. These need to be added to DMSR. See [LCR-581|https://docushare.lsstcorp.org/docushare/dsweb/Get/Version-37829/LCR-581CalibrationHardwareRequirementsUpdateApproved.pdf]."
Answer: 37808.0

User story: "https://project.lsst.org/onboarding/form"
Answer: 15.0

User story: "I've stumbled across {{post-qa 1.2.0}} returning a less than help error message when the http basic auth credentials are rejected:    {code}  {('Connection broken: IncompleteRead(0 bytes read)', IncompleteRead(0 bytes read))  {code}    An error message and/or http status code similar to what is printed upon success would be a major improvement.  E.g.:      {code:java}  POST https://<USER>larry-squash.lsst.codes/dashboard/api/jobs/ status: 201  {code}  "
Answer: 1048687.0

User story: "The {{lsst_dm_stack_demo}} scripts need some minor fixes to make them work on Python 3."
Answer: 196.0

User story: "On the Verification Cluster, run ProcessCcd with a small set of real HSC data using Pegasus. "
Answer: 41733.0

User story: "Currently the interface of generating Pegasus XML is  {{python path/generateDax.py -i path/inputData.py -o outputXml.dax}}  The input data file contains data id information and is an input of the more generic Pegasus dax generating script.  While the exact format of this file (or non-file) is TBD, in this ticket I shall clean up the inputData file of the DM-8603 workflow to contain only data and no codes. This ticket provides a a stop-gap. "
Answer: 17428.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: "Having a default constructor to Footprints would be useful in many cases. Add one which takes only a PeakSchema as a default argument, and creates a null SpanSet"
Answer: 7118.0

User story: "I have apparently been included as an author of [LDM-151|https://ldm-151.lsst.io/v/draft/LDM-151.pdf] for [a long time|https://github.com/lsst/LDM-151/commit/4eea5b1e29f8b82579d82560c89c33317e52e182], but to my knowledge have never contributed a word.  I suggest that I should be removed from the author list."
Answer: 137343.0

User story: [~<USER> made the observation in a c.l.o. post that our weekly tag format could be more "sorting" friendly:    bq. Since I have your attention, would you consider using fixed-length weekly tags, such as w_2017_05 instead of w_2017_5, consistently to what was done for weekly tags in 2016? The motivation is that over time we will have several of those versions installed and it will be easier for the end user to find a given version among the available ones, given the lexicographical order used by default by the ls command and even when browsing the tags repository at https://sw.lsstcorp.org/eupspkg/tags.
Answer: 274838.0

User story: "Currently, we require that the matching kernel has smaller dimensions than the PSF.   https://github.com/lsst/ip_diffim/blob/da2cd4f0fcee785084b03b5e20f5a72f1bb85190/src/KernelSolution.cc#L318    There's a tradeoff between pixels being fit and kernel size. When kernels are too small matched-PSFs look square, but they can't be arbitrarily big. This makes the window of appropriate kernel sizes vary narrow, and in some cases non-existent.     This ticket will pad the PSF before matching and test whether this solves the matching problems observed matching HSC PsfExPsfs."
Answer: 88016.0

User story: "With the adoption of RFC-34 the developer guide needs to be updated with the new guidance.    [~<USER> I'm assigning this to team DRP at the moment on the basis that it was triggered by [~<USER>. We can obviously negotiate."
Answer: 1795564.0

User story: "There are cases where we would like objects that contain floats whose value is NaN. The idea was to add a comparison method {{bool nanSafeEqual(<type> const & other) const;}} to AFW objects where if a data member is a float and in the body if {{this->myFloat != other.myFloat}} then it would also check to see if {{this->myFloat}} is NaN AND {{other.myFloat}} is NaN, in which case these two objects would be treated as equivalent.    This was identified in {{obs_test/tests/testMetadataObjectAccess.py}}, which currently works around the problem by testing members of a {{VisitInfo}} object directly. Once this is done that test should be updated. Note that writing {{nanSafeEqual}} in {{VisitInfo}} will require writing {{nanSafeEqual}} for some of its data member types as well."
Answer: 1791494.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: "Using the NumPy C API requires some ugly boilerplate in every wrapper file that uses the ndarray type_casters.  pybind11 provides its own low-level numpy interface, and it'd be better to use that instead.  I imagine this will uncover some functionality we'd want to add to upstream pybind11, but I imagine we'd at least have the option of doing that locally if that isn't a possibility."
Answer: 541631.0

User story: "Move the Fastly API client for CDN purges from LTD Keeper to the common LTD Conveyor package so that both Keeper and Dasher can perform purges."
Answer: 1791.0

User story: "The current structure of the jenkins {{weekly-release}} job is to publish eupspkgs/tag + apply a git tag after a successful {{lsstsw}} based build.  However, it has become clear that this will not catch all possible breakage of {{newinstall.sh}} based {{eups distrib install}} s.  The {{weekly-release}} job should be refactored to do a {{newinstall.sh}} canary build (throw away) based on the candidate {{bNNNN}} number before an eups distrib tag is published and the the git repos are tagged."
Answer: 707275.0

User story: "According to a quick grep, we do not currently use the ra/dec to/from string routines in utils anywhere in lsst_apps, and I think it's unlikely we use them anywhere in the stack.  Moreover, if we did need these routines in Python, we could now rely on code in Astropy to do it.    This change requires an RFC to hopefully catch any usage my grep may have missed."
Answer: 1791535.0

User story: "Should improve the Python interface and reduce copying."
Answer: 547749.0

User story: "{{afw::geom::Functor}}, which is used by {{SeparableXYTransform}} as an interface for 1-d coordinate transformations, can be completely replaced by new standard library functionality.    Should consult with [~<USER>, who is (to my knowledge) the only current user."
Answer: 1791541.0

User story: "The pybind11 port adds keyword arguments to most calls, making {{afw.image.makeVisitInfo}} obsolete.  Remove it."
Answer: 1913168.0

User story: Per request from [~<USER> & others, folks would like to be able to track their "science time" projects in JIRA. Figure out if this could cause any problems and distribute guidelines.
Answer: 45.0

User story: "At the moment, when running an LSST task, {{Executor}} always creates a dataset repository from scratch.  This prevents it from using existing dataset repositories. "
Answer: 3.0

User story: "The middle of the S17 cycle falls at the end of February. Ensure that plans for the next three months are fully mapped out by mid-month and work with Kevin to submit the relevant LCR."
Answer: 29197.0

User story: "Considering amount of various data which will be passed to the Executor, initially selected method of doing it (command line arguments) turned out to be cumbersome and error prone. The goal is to replace it with more robust approach, e.g., an input file. "
Answer: 12.0