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: "After DM-10271, detection will have two sources of inefficiency due the limitations of lower-level algorithms:   - Because there's no way to tell SubtractBackgroundTask to just estimate the background without subtracting it, we do an unnecessary subtract and add of a large image.   - Because there's no way to tell the thresholding code to find Footprints without finding Peaks, we waste time looking for Peaks we'll throw away when doTempLocalBackground is True.   - Because there's not way to tell the thresholding code to find Peaks within an existing Footprint, we waste a *lot* of time (80% of the total runtime of SourceDetectionTask) transferring overlapping Peaks from one set of Footprints to another.  "
Answer: 1088.0

User story: "[~<USER> reports that the header of latex documents using the {{lsstdoc}} class file is inconsistent leading to the document information sometimes crushing into the blue horizontal rule."
Answer: 3220.0

User story: "Implement the translation operator and algorithm designed in DM-10189."
Answer: 161013.0

User story: "It would be useful to have a baseline for seeing the difference between running a group of queries using shared scans and without using shared scans."
Answer: 56219.0

User story: "We need to include saturation trails and the scattered light off the channel stops in the y-band in {{BRIGHT_OBJECT}} masks.    Please add support for {{box}} in {{ObjectMaskCatalog}} and {{AssembleCoaddTask.setBrightObjectMasks}}.   In general these boxes will *not* be axis aligned, but for an initial implementation it is sufficient to assume that {{angle==0}}, pending the resolution of DM-10307.    At the same time, please allow the input {{ds9}} region files to specify a magnitude in the comment, following the {{id}} field.  "
Answer: 1244.0

User story: "In lieu of a provenance system, the verification framework will use metadata to distinguish measurements and enable specifications to act only up on certain measurements.    This will    * Add Job.meta, to add metadata at a Job level  * Add Measurement.meta to add metadata at a measurement level. Measurement metadata is also available from Job.meta by prefixing it with the metric name.  * Create a MetadataQuery to filter Measurements that apply to a specification."
Answer: 9357.0

User story: "Update firefly_widgets to account for some changes in external dependencies:    * Generalize the connection parameter, for working with Firefly servers now being deployed with {{suit}} or {{irsaviewer}} in the URL, as was done for firefly_client in DM-9843  * Make some minor syntax changes to work with ipywidgets 6.0  * Update example notebooks accordingly"
Answer: 10051.0

User story: "Following RFC-188 and discussion the 2017-04-17 DMLT meeting, discuss options for the DM release process with stakeholders and create a technote summarising important considerations."
Answer: 4192.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This is the implementation ticket for RFC-322. The implementation is as follows:    * Rename all of our {{*Flux_flux}}/{{*Flux_fluxSigma}} table fields to {{*Flux_instFlux}}\{{*Flux_instFluxSigma}} to hold the post-ISR counts.  * Add {{*Flux_flux}} and {{*Flux_mag}} fields for the post-calibrated flux (in Maggies) and magnitudes.  *Rename the {{InstFlux}} slot to {{GaussianFlux}}, and remove the {{InstMag}} slot.  * Add associated documentation to the above.  * Pass these changes on to the relevant database groups to update e.g. {{cat}}.    Implementing this will wait until Calib is removed from the stack and replaced by PhotoCalib (not yet scheduled, but likely within the next couple months)."
Answer: 743454.0

User story: "We have the crosstalk coefficients for DECam, but do not apply them by default.  This is an obvious problem for images with saturated stars.  We should turn that correction on by default, and if possible port the solution to {{ip_isr}}."
Answer: 489471.0

User story: "In the example image I'm looking at for the prototype system, I noticed that one of the tape bumps is not masked.  There appears to be a mask for it, but it does not show up in the correct place.  My suspicion is that the defects may be supplied in one coordinate system and applied in another (e.g. trimmed vs untrimmed).    Here's an image from CCD 28 from a visit in Blind15A_38."
Answer: 7055.0

User story: "When looking at outputs of the alert production pipelines, we noticed that there appear to be two different sets of treerings in the image.  Here is a screenshot from DS9 stretched to show them better: !double_treerings.png|thumbnail!.  These data are from CCD 28 of one of the visits in field Blind15A_28.    My guess is that we are applying the wrong flat to these images.  It may be related to the HDU index reordering."
Answer: 7288.0

User story: "metaserv table listing uses {{information_schema}}. It should utilize DBRepo and DDT_Table in metaserv."
Answer: 8812.0

User story: "Refine database description, needs, and uses table based on first round information."
Answer: 1.0

User story: "The {{ast::FrameSet}} returned by {{Transform.getFrameSet}} is not immutable in Python, and modifying it modifies the frame set owned by the transform. In C++ the returned FrameSet is immutable, but that is impossible to enforce in Python, so the obvious fix is for the Python wrapper to return a copy."
Answer: 174.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: "Czars can have difficulty handling large results. The real solution for this is multiple czars, as dozens of workers producing numerous result rows will be able to overwhelm a single czar. However, the behavior of each czar needs to reliable and consistent even when handling multiple user queries that each generate large results.    Currently, the czar has trouble sending tasks for new user queries once it is dealing with a certain number of large result user queries. It is desirable to tasks for new user queries out as quickly as possible so that workers can start processing them, and also to know at what point a czar should stop accepting user queries.  It would be vary useful to know what is causing the current bottleneck.    The czar can handle several user queries that return large results on the larger tables (Source and ForcedSource). It has more trouble with multiple large result queries on the smaller Object table. The reason for this being that user query returning a million rows from Source may take half an hour to run on the workers, while a million rows from Object will take less than 10 minutes. The queries aren't done at that point as the results from all the jobs in each user query are trickled back to the czar, but the initial transmits from each query are apparently enough to cause the czar difficulty.    "
Answer: 324277.0

User story: This is a trivial feature request that would have also been very useful on DM-9962.  In terms of effort it should be "in the noise" of everything else blocking DM-10266, so I'm going to try to get it in.
Answer: 2123.0

User story: "The non-backported cmake from the regular jessie ppa is binarily incompatible with the modern libcurl which is now provided as an eups package    "
Answer: 974.0

User story: "Currently {{lsstlaunch.sh}} will load the current version of {{lsst_distrib}} before starting the python kernel.  This makes the stack environment available in the notebook, but it's not easy for a user to stick in their own packages.    One way to do this is to modify {{lsstlaunch.sh}} to look for a special file in the users home directory and source it.  E.g. {{lsstlaunch.sh}} could look like  {code:shell}  #!/bin/bash  set -x  source /opt/lsst/software/stack/loadLSST.bash  source eups-setups.sh  setup lsst_distrib  if [ -f $HOME/.user_setups ]; then      source $HOME/.user_setups  fi  exec python -m ipykernel -f $1  {code}    Then in the user's home directory there could be a file called {{.user_setups}} that looks like:  {code:shell}  setup foo  setup -r /path/to/code/repository  {code}"
Answer: 11293.0

User story: "Search the image meta data for WISE coadd and single frame images  Able to access IRSA IBE service to get the images and display them."
Answer: 47249.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: "Joins between two databases are not working. On the PDAC, stripe82 cannot be joined with WISE, despite using identical partitioning methods. This is probably a result of an expectation that qserv would onlt access one database at time.    An example of this would be an attempt to figure out all entries from the *ForcedSource* table of *WISE* catalog (database *wise_00*) which correspond to the _rejected_ objects of the catalog (those objects live in a separate database *wise_ext_00*):  {code:sql}  SELECT COUNT(ForcedSource.source_id_mf)    FROM      wise_ext_00.Reject Reject,      wise_00.ForcedSource ForcedSource    WHERE      Reject.source_id LIKE '0000m016_ac51-000002'    AND ForcedSource.source_id_mf = Reject.source_id;  ERROR 4110 (Proxy): Query processing error: QI=?: Failed to instantiate query: AnalysisError:Query involves  partitioned table joins that Qserv does not know how to evaluate using only partition-local data  {code}    The only relevant line in the *CZAR*'s log file is:  {code}  [2017-04-21T16:01:43.412-0500] [LWP:346] ERROR ccontrol.UserQueryFactory (core/modules/ccontrol/UserQueryFactory.cc:114)  - Invalid query: AnalysisError:Query involves partitioned table joins that Qserv does not know how to evaluate  using only partition-local data  {code}"
Answer: 41620.0

User story: "DM-10122 and DM-7468 implement StorageInterface for mysql and swift, and initial formatters for AFW table objects.     In response to this, the StorageInterface abc and mysql and swift subclasses should be documented, as well as their relationship to formatters."
Answer: 326170.0

User story: "Because JupyterLab allows access to a shell, it would be nice to have a way to tell users of the shell where to find the stack.  I think just adding a message to the {{/etc/motd}} giving paths to the various stacks installed in the instance would be sufficient."
Answer: 7526.0

User story: "All of the removed distrib tags seem to have magically reappeared on their own in the last day or so.  Presumably, this is somehow related to the NFS -> GPFS move."
Answer: 1488.0

User story: "When a chart is plotly chart, image download button should be present on it's toolbar.  Start with png and jpeg (which require no payment plan)."
Answer: 22971.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: We are unable to build on el6/py3 as the {{scons}} product's {{eupspkg.cfg.sh}} references {{python2.7}}.  The system python interpreter on el6 is {{python2.6}}.  If scons is still compatible with 2.6, and we want to support the combination of el6/py3 (???), this could be fixed by changing the interpreter to be {{python2}}.    {code:java}  [el6] ***** error: from /build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/build.log:  [el6] ++ debug 'CC='\''cc'\'''  [el6] ++ [[ 3 -ge 2 ]]  [el6] ++ echo 'eupspkg.dumpvar (debug): CC='\''cc'\'''  [el6] eupspkg.dumpvar (debug): CC='cc'  [el6] + for _VAR in '"$@"'  [el6] + eval 'debug "CXX='\''$CXX'\''"'  [el6] ++ debug 'CXX='\''c++'\'''  [el6] ++ [[ 3 -ge 2 ]]  [el6] ++ echo 'eupspkg.dumpvar (debug): CXX='\''c++'\'''  [el6] eupspkg.dumpvar (debug): CXX='c++'  [el6] + for _VAR in '"$@"'  [el6] + eval 'debug "SCONSFLAGS='\''$SCONSFLAGS'\''"'  [el6] ++ debug 'SCONSFLAGS='\''opt=3'\'''  [el6] ++ [[ 3 -ge 2 ]]  [el6] ++ echo 'eupspkg.dumpvar (debug): SCONSFLAGS='\''opt=3'\'''  [el6] eupspkg.dumpvar (debug): SCONSFLAGS='opt=3'  [el6] + build  [el6] + python2.7 setup.py build  [el6] /build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/scons-2.5.0.lsst2+1/ups/eupspkg.cfg.sh: line 5: python2.7: command not found  [el6] + exit -4  [el6] eups distrib: Failed to build scons-2.5.0.lsst2+1.eupspkg: Command:  [el6]  source "/build/eups/bin/setups.sh"; export EUPS_PATH="/build"; (/build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/build.sh) >> /build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/build.log 2>&1 4>/build/EupsBuildDir/Linux64/scons-2.5.0.lsst2+1/build.msg   [el6] exited with code 252  [el6] Removing lockfile /build/.lockDir/exclusive-root.631  {code}  
Answer: 273829.0

User story: "Our current implementation of the temporary local background approach to avoiding spurious detections near bright objects simply subtracts a local background from the full image before performing any detection steps.  That can result in missed isolated-object detections and incorrect Footprints for large objects.    Instead, we should:  1. Detect Footprints and Peaks.  2. Subtract the local background.  3. Detect Peaks within each Footprint again, and use the new set of Peaks instead of the old set if and only if there is at least one Peak in the new set.    This really ought to be fixed before the HSC internal release or major HSC processing at NCSA."
Answer: 4535.0

User story: "At least some of the implementation was in    $OBS_SUBARU_DIR/python/lsst/obs/subaru/ingest.py    on the old HSC fork."
Answer: 30646.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> has fixed some critical problems in meas_mosaic and coaddition, so it's time for a new release.  I'm also hoping to include a blendedness bugfix that should be trivial.    I do not think we'll get PostgreSQL registry support into this minor release (I don't know how much work it will be, so I don't want to assume it's trivial).    We should also need to add {{display_ds9}} to hscPipe on this release.    [~price], I'm planning to work on this today unless I hear from you that you're back in town and available to work on it.  If you do work on it, we should make sure we sync our versiondbs first so we don't make anyone install anything unnecessary due to spurious version changes."
Answer: 5607.0

User story: "There's some documentation at https://github.com/lsst/afw/blob/1d3521f81d348fdc49b708342eba0be1caf5295b/doc/tablePersistence.dox which seems useful, but is basically impossible to find in Doxygen. Let's include it on the list at https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/afw.html."
Answer: 29.0

User story: "Unplanned Supertask/Butler Working Group meetings for April."
Answer: 11669.0

User story: "While nothing in qserv yet depends on libcurl, features currently being developed on branches do depend on it.    Since libcurl is not yet an eups dependency of qserv on master, it does not get pulled into the qserv:dev base container.  Since the qserv:dev base container is used identically by Travis CI on all branches including master, Travis is currently broken on development branches that depend on libcurl, and would be broken after merge of any of these branches to master for at least on container build iteration.    Checking in the table file dependency on master ahead of any code which depends on libcurl allows us to use Travis during branch development and will avoid any Travis burps at such time as dependent branches are merged."
Answer: 18.0

User story: "https://github.com/lsst-sqre/post-qa originated as an independent repo when the verification framework was embedded inside {{validate_drp}}. Now that {{lsst.verify}} is its own framework, it makes sense to move the verification framework's REST client to https://github.com/lsst/verify    At the same time, we can make improvements    - name the command {{dispatch_verify.py}} so it doesn't imply a post-processing step.  - Use {{lsst.verify}} classes directly.  - Less re-shaping of the JSON; lets try to ensure that JSON created by {{lsst.verify.Job}} is exactly what's needed from the SQUASH HTTP API."
Answer: 13145.0

User story: "create the package described by RFC-328"
Answer: 1126.0

User story: "Following the experiment with devtoolset in DM-9955, can we please install devtoolset-4 and devtoolset-6 on lsst-dev so that we can expand our testing of new compilers."
Answer: 63224.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 jenkins node running as {{lsstsw@lsst-dev}} used for publishing eups distrib packages is unable to build from current master, thus preventing the weekly release process.  Speculation is that some installed products were built from a mixture of the system gcc and devtoolset-3."
Answer: 1349.0

User story: "For evolvability, we need to track the serialization version of persisted datasets  with the datasets in the database.    This will be at least partly implemented by the daf_io afw_table database serializer & deserializer. If there are any requirements imposed on {{daf_fmt_mysql}} or Butler this is the story to implement those."
Answer: 308308.0

User story: "We need to be able to put a registry in a mysql database and access it via MySqlStorage.     TBD if this should be done by refactoring or duplicating the sqlite registry to work with mysql, or if there should be a formatter to write sqlite3 registries to mysql databases. Or, if it should be done another way."
Answer: 308315.0

User story: "When using nested serializers in DRF the queries involving multiple tables can be improved using the {{prefetch_related()}} method from the Django QuerySet API which automatically retrieve related objects in single batch.    https://docs.djangoproject.com/en/1.11/ref/models/querysets/#prefetch-related    Also drf-extensions package can be used to enable cache in SQUASH REST API at the view level.    http://chibisov.github.io/drf-extensions/docs/#cacheresponsemixin    A useful tool to monitor the queries that are executed when accessing the API endpoints is the Django debug toolbar:    https://django-debug-toolbar.readthedocs.io/en/stable/"
Answer: 459.0

User story: "Get kubespawner creating instances on demand.  Not OAuth-integrated at this stage."
Answer: 10162.0

User story: "In http://irsawebdev1.ipac.caltech.edu/firefly/;a=layout.showDropDown?visible=false, search for image: RA = 45, Dec = 89, select IRAS with 5 degree cutout; Add grid, add the North/East compass. The East arrow line should be perpendicular to the North arrow line. "
Answer: 14059.0

User story: "Per RFC-318"
Answer: 166846.0

User story: "As stated in DM-9862, meas_mosaic assumes the 0,0 for each CCD to be the lower left hand corner.  LSST uses a different coordinate system so meas_mosaic rotates the wcs into the LSST frame when writing to disk.  However the photometric correction is still in the HSC frame, so when applying the meas_mosaic correction we need to rotate the wcs back to the HSC frame.  We can then create the photometric correction, rotate it into the LSST frame and apply it to the image.  We then rotate the wcs back to the LSST frame."
Answer: 5077.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In DM-9855, the option to select input images based on PSF quality was added and made the default for assembleCoadd in obs_subaru.  However, coaddDriver has its own function to select images and sets the one in assemble coadd to null.  The config in obs_subaru was overriding this and the selection of images was being run twice and having strange results.    The resolution is to set the image selector in coaddDriver to the PSF quality selector and set the assembleCoadd selector to null."
Answer: 5088.0

User story: A while back, I wrote some (brief!) notes on {{lsstDebug}}, which I think are more helpful than https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/base_debug.html. Rather than having them get lost, let's see if we can add them to the Dev Guide.    (Ultimately, they should be in a "framework" section of the pipelines docs, à la DMTN-030. But that doesn't exist yet.)
Answer: 3069.0

User story: "getInfoFromMetadata() throws away errors without warning. This makes debugging writing translator functions very hard."
Answer: 35.0

User story: "DM-9812 added a new dataset {{srcMatchFull}} to {{ci_hsc}}.  Update the Pegasus ciHsc workflow to be consistent. "
Answer: 126522.0

User story: "Move the sim_data dataset:  1. Work with simulation team (Scott and Peter) to get the exact destination location to transfer their data.  2. sync files  3. Update services to point to the new data location  4. Move old data to the actual NFS server.  5. Contact the data owner that migration is completea"
Answer: 14.0

User story: "{{jointcal}} uses inconsistent code layout that is furthermore incompatible with the DM C++ Style Guide.  Running {{clang-format}} on it would greatly improve code readability and maintainability."
Answer: 70629.0

User story: "Ingest {{IMGTYPE}} along with other header keys. Add a translator so that these end up with useful/sane values."
Answer: 5591.0

User story: "Investigate file replication software for possible use in DBB archive system, e.g., Xtreemfs, GlusterFS, and SymmetricDS."
Answer: 20299.0

User story: "As described in DM-5902 it is very useful to be able to specify arbitrary registry keys in the {{--id}} of e.g. {{constructBias.py}}.  Unfortunately only keys that are returned by {{butler.getKeys}} for the appropriate dataset type are currently accepted, even if other keys would be sufficient to define the desired data.    Please fix this.  "
Answer: 66.0

User story: "Finalize plans for acquisition, shipping, travel, and deployment. Determine actions needed to comply with shipping requirements (packaging and timing), for personnel needed to perform the installation, etc.    Coordinate wth NCSA Security, Networking, and System Engineering, as well as with project and base site personnel."
Answer: 30257.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 project use cases and requirements, develop detailed list of equipment needed to deploy initial AA/IM capability at base site in Chile. Coordinate with NCSA Security, Networking, and System Engineering, with input from project staff in Tucson and Chile."
Answer: 30152.0

User story: "In order to annotate LSE-63 with requirements I need to locate the source from [~tony], add it to github and make it work with the new Latex look and feel."
Answer: 186.0

User story: "We are currently working on SQUASH stability (DM-9651) and usability (DM-10176) improvements and we should plan at least two production updates during those epics which together represent ~30 SP of work.    The first update S17-1 would bring to production the tickets listed below."
Answer: 767709.0

User story: "Currently Executor does not support any logging which makes tracking execution/debugging rather hard. The goal is to add a logger which would allow for easy monitoring of an Executor run."
Answer: 60339.0

User story: "Review existing policy.  Make changes as necessary to comply with LSST project and NCSA requirements.  Obtain project concurrence as necessary."
Answer: 31686.0

User story: With the individual FGCM modules in place, they need to be linked together for a complete "fit cycle" where stars are read in, good exposures are selected, fit parameters are updated, and zeropoints are computed.  
Answer: 27629.0

User story: "Memory locking should be controlled inside containers"
Answer: 27458.0

User story: "The production LSST Git LFS server failed today at 5:52 AM MST. It was Nebula instance <USER>ubuntu-git-lfs-test (e20a71e1-7885-4b27-9781-43e2442cd432 141.142.210.114 https://git-lfs.lsst.codes https://git-lfs-test.lsst.codes). It failed due to a corrupt root filesystem. Grub 2 could not identify a viable boot disk.    This resulted in approximately five hours of downtime.    It was rebuilt as Nebula instance (90cc6090-4b04-4aab-a956-d9d5b57c31b2 141.142.211.1 https://git-lfs.lsst.codes).    Further investigation is possible. The bad instance (e20a71e1-7885-4b27-9781-43e2442cd432) still exists on Nebula."
Answer: 937095.0

User story: "If I try to create a histogram chart with x axis set to be 'log' from the tri-view viewer,  no histogram chart is rendered.   This issue is found by doing the following,   step 1: Do catalog search, such as m31 and cone size is 200 arcsec.   step 2: add a histogram chart  to the tri-view viewer:                   - click 'Charts' from the menu to get chart selection dropdown window.                  - select 'histogram' and column 'dec'                   - set x axis to be 'log',                   - click OK button.      Some numbers are filled into the fields of 'Min', 'Max', and 'Bin width' when 'histogram' and a single column name are selected from the 'Charts' dropdown window. However those numbers are only applicable to the case when x is linear scaled and they are not suitable when x is selected to be 'log'.   "
Answer: 18357.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 root filesystem became read-only on instance [p-es-k-<USER>6dfaab48-aadf-4135-b933-23844685922b 141.142.209.207 logging.lsst.codes].    The read-only filesystem resulted in crashing Kibana. After a restart I was required to manually run fsck.ext4. See attached images. The other master elasticsearch nodes continued to function with a few exceptions. There was approximately an two hours of downtime with Kibana. Since Logstash was running logs were only affected twice at approximately 05:40-06:00 MST and 15:20-15:40 MST."
Answer: 1509302.0

User story: "The recent implementation of DM-9952 caused the ingestCalibs config in obs_decam to break when ingesting defects (and possibly other calibration products too). A quick fix should adjust the default HDU indexing to begin at 0 instead of 1."
Answer: 1563.0

User story: "The LSST Git LFS server failed today at 5:52 AM MST. It was Nebula instance <USER>ubuntu-git-lfs-test (e20a71e1-7885-4b27-9781-43e2442cd432 141.142.210.114 https://git-lfs.lsst.codes https://git-lfs-test.lsst.codes). It failed due to a corrupt root filesystem. Grub 2 could not identify a viable boot disk.    It was rebuilt as Nebula instance (90cc6090-4b04-4aab-a956-d9d5b57c31b2 141.142.211.1 https://git-lfs.lsst.codes).  "
Answer: 24.0

User story: "TBD"
Answer: 948928.0

User story: "The root filesystem became read-only on instance [p-es-k-<USER>6dfaab48-aadf-4135-b933-23844685922b 141.142.209.207 logging.lsst.codes].    The read-only filesystem resulted in crashing Kibana. After a restart I was required to manually run fsck.ext4. See attached images. The other master elasticsearch nodes continued to function with a few exceptions. There was approximately an two hours of downtime with Kibana. Since Logstash was running logs were only affected twice at approximately 05:40-06:00 MST and 15:20-15:40 MST."
Answer: 30.0

User story: Watching a video about mastering Django from O'reilly Safari there's an interesting solution to reduce code duplication when you have views acting on the same set of data but returning slightly different results. The technique is called "switchboard view"    https://www.safaribooksonline.com/library/view/mastering-django-web/9781783989805/video1_5.html    this ticket will solve the code duplication we have in the squash views by replacing the endpoints {{api/AMx}}, {{api/PAx}}, used to retrieve data for the bokeh apps, by a single endpoint {{api/apps}}.    
Answer: 30243.0

User story: Improve integration of {{lsst.verify.Measurement}} into the new {{lsst.verify}} API design.    Goals:    - Make the "check" method against Specifications consistent with Specification.check().  - Make "extras" persist into a per-measurement Blob instead of an adhoc measurement data container.  - Review serialization and deserialization.  - Make MeasurementSet consistent with MetricSet and SpecificationSet.  - Refine the story for {{output_measurements()}} given the full API.
Answer: 18492.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: "On reading LDM-151, I asked [~<USER> a question about how flat-fields were being applied. He's provided some updated text. On this ticket, we'll include it in the document."
Answer: 39.0

User story: "I realized that not {{__ne__}} is not automatically implemented when {{__eq__}} is implemented. This can cause unexpected behavior with the {{!=}} operator.    This ticket implements {{__ne__}} in existing classes in verify.    I also implements {{__lt__}}, {{__le__}}, {{__gt__}}, and {{__ge__}} operators to the Name class to support Name sorting."
Answer: 2539.0

User story: "Quick fix to remove an attempt to import subaruLib. Blocking ci_hsc on my laptop. "
Answer: 20.0

User story: "Given the documentation content made in DM-10144, this ticket will deploy those docs to https://lsst-texmf.lsst.io (LSST the Docs). Also included in the scope are adjustments to the Sphinx site and including example PDFs in the distribution."
Answer: 21233.0

User story: "Prune the set of published EUPS distrib tags per RFC-316."
Answer: 18.0

User story: "One of the major flaws in the current deblender is that it assumes the peaks passed to the function are the correct peak locations for the center of each object. This is wrong in the sense that    # Sometimes the position is grossly incorrect, as the peak position can be off by as much as a pixel or two from the true peak  # Even when the peak position is close, the actual source is always at some fractional pixel position, so the symmetry constraint can fail to converge for sources offset by nearly half a pixel.    [~<USER> and I propose to implement a translation operator that will allow templates to be shifted by up to 2 pixels by rational numbers in {{x}} and {{y}}."
Answer: 18506.0

User story: "Fix two drawing related issues with the new rotation scheme      - marker resize handles off when rotated   - footprint rotate handles off when rotated    Check both wit flip as well.     Also check if the region code is working the flip and rotate.      This ticket should be done as a pull request against branch dm-10065-canvas instead of dev."
Answer: 21713.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 WISE dataset uses fixed precision decimals and dbserv doens't properly handle them when serializing to JSON.      {code}  [2017-04-11 16:52:06,003] ERROR in app: Exception on /db/v0/tap/sync [POST]  Traceback (most recent call last):    File "/lsst/stack/Linux64/flask/0.12/lib/python/Flask-0.12-py2.7.egg/flask/app.py", line 1982, in wsgi_app      response = self.full_dispatch_request()    File "/lsst/stack/Linux64/flask/0.12/lib/python/Flask-0.12-py2.7.egg/flask/app.py", line 1614, in full_dispatch_request      rv = self.handle_user_exception(e)    File "/lsst/stack/Linux64/flask/0.12/lib/python/Flask-0.12-py2.7.egg/flask/app.py", line 1517, in handle_user_exception      reraise(exc_type, exc_value, tb)    File "/lsst/stack/Linux64/flask/0.12/lib/python/Flask-0.12-py2.7.egg/flask/app.py", line 1612, in full_dispatch_request      rv = self.dispatch_request()    File "/lsst/stack/Linux64/flask/0.12/lib/python/Flask-0.12-py2.7.egg/flask/app.py", line 1598, in dispatch_request      return self.view_functions[rule.endpoint](**req.view_args)    File "/lsst/stack/Linux64/dax_dbserv/12.1-2-gb29d23c+10/python/lsst/dax/dbserv/dbREST_v0.py", line 98, in sync_query      return _response(response, status_code)    File "/lsst/stack/Linux64/dax_dbserv/12.1-2-gb29d23c+10/python/lsst/dax/dbserv/dbREST_v0.py", line 138, in _response      response = json.dumps(response)    File "/lsst/stack/Linux64/miniconda2/4.2.12.lsst1/lib/python2.7/json/__init__.py", line 244, in dumps      return _default_encoder.encode(obj)    File "/lsst/stack/Linux64/miniconda2/4.2.12.lsst1/lib/python2.7/json/encoder.py", line 207, in encode      chunks = self.iterencode(o, _one_shot=True)    File "/lsst/stack/Linux64/miniconda2/4.2.12.lsst1/lib/python2.7/json/encoder.py", line 270, in iterencode      return _iterencode(o, 0)    File "/lsst/stack/Linux64/miniconda2/4.2.12.lsst1/lib/python2.7/json/encoder.py", line 184, in default      raise TypeError(repr(o) + " is not JSON serializable")  TypeError: Decimal('0.000') is not JSON serializable  {code}
Answer: 24754.0

User story: The Docushare bibtex entry inherited from Gaia has some cruft that should be cleaned up. Currently it looks like:    {code}  @DocuShare{LDM-156,  author = {Jonathan Myers and <USER>and Tim Axelrod},  title={Moving Object Pipeline System Design},  year={2013},  month=oct,  url={http://ls.st/LDM-156},  note={},  llnote={},  docusharenumber={LDM-156},  docushareshortnumber={{LDM-156}}  }  {code}    which has too much duplication of the document handle. We need to end up with something like:    {code}  @DocuShare{LDM-156,  author = {Jonathan Myers and <USER>and Tim Axelrod},  title={Moving Object Pipeline System Design},  year={2013},  month=oct,  note={},  docusharenumber={LDM-156},  }  {code}  Additionally, the official term for the document number is the "handle" in DocuShare so {{docusharenumber}} should be replaced with {{handle}}.  
Answer: 1617.0

User story: "Create Kubernetes template for Jupyterlab demo"
Answer: 430.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: "ndarray is being built with {{-DNDARRAY_SWIG=ON}}, and hence carrying a Swig dependency. It's (probably) the only thing in lsst_distrib that carries that dependency, and, following the pybind11 merge, it should be unnecessary. Remove it, and drop Swig from the distribution."
Answer: 182594.0

User story: "Since Archiving has been fully prototyped, there are some requirements to add into the other commandable devices to keep the system up to date. In addition, the separation of the base foreman into individual devices requires that the DMCS scoreboard schema be modified."
Answer: 71903.0

User story: "Change overall look and feel to responsive-design best-practices looks as these are more familiar to uses especially from mobile clients."
Answer: 73683.0

User story: "Use bokeh templates to create this page layout for the drill down plots.    [https://bokeh.pydata.org/en/latest/docs/user_guide/embed.html]"
Answer: 952017.0

User story: "Install GIT and auto pull scripts so that fresh src code is available on the L1 test network"
Answer: 3.0

User story: "New version of bokeh released, updating from 0.12.3 to 0.12.4.   "
Answer: 1713.0

User story: "Set up message brokers, Redis instances and InfluxDB along with user accounts and keys for each."
Answer: 18.0

User story: "Install new L1 system code across subnets 237.* and 238.*"
Answer: 71924.0

User story: "Occasional needs for Integration activity address, such as pulling down new OCS releases, writing supporting documents, etc."
Answer: 71929.0

User story: "Build Event publisher for OCS Bridge."
Answer: 83588.0

User story: "Removing Pika/Python Consumer code from OCS Bridge and replace with C++."
Answer: 4.0

User story: "Support for new OCS commandable entity hierarchy."
Answer: 14.0

User story: "Review FY17 plan; get updated vendor quotes as needed. This is for the temporary loaner system as well as the follow-on ful (40+) system."
Answer: 36188.0

User story: Current implementation of the generic DAX generator accepts only {{networkx.DiGraph}} as an input. The goal is to implement ability to support importing graphs expressed in a few "standard" formats, starting with [GraphML|http://graphml.graphdrawing.org/].  
Answer: 15978.0

User story: Search and replace all "Calib" with "PhotoCalib", delete the Calib tests from {{afw/tests/testColors.py}}, delete all the Calib code ({{include/Calib.h}}, {{src/Calib.cc}}, {{python/calib.cc}}), and then see what breaks. The API is now quite different and it's immutable, so there are going to be quite a few more changes necessary. Hopefully most of them can be taken care of by globally replacing "getMagnitude" with "countsToMagnitude", but we'll see.
Answer: 1046793.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 two `countsTo*` methods that operate in-place on SourceCatalogs in PhotoCalib are marked "not implemented" due RFC-322. Once that RFC is completed and the necessary key name changes are in place, we can finally implement those methods.    We might want to consolidate them into a single {{countsToFluxAndMagnitude}}, since if we're iterating over the catalog anyway, might as well do all the math at once.
Answer: 1073324.0

User story: "The current symmetry operator work by comparing each pixel to its symmetric partner and projecting the difference to zero using a proximal operator, forcing the solution to be symmetric. This works relatively well, but not as well as the current deblender in certain cases. For example, in a blend with only two sources, with one source much brighter than the other, the faint source using the NMF deblender attempts to steal a small amount of flux from its brighter neighbor. We had hoped that the near zero flux opposite the bright source would be enough to limit this effect (when combined with symmetry) but the algorithm breaks when the fainter object wants to steal flux near the same level as the noise. Sparsity is not much help, as l0 sparsity limits the size of brighter objects more than the smaller ones.    This blending issue is accounted for in the current deblender (adapted from SDSS) because it doesn't just force a symmetric solution, it forces the symmetric solution to use the minimum of each pixel and its symmetric partner. This is a much stronger constraint (and more useful) constraint.    It would be useful to update the NMF deblender to have the same minimum pixel value constraint. One way to do this is to use a proximal operator that projects each template onto a space that uses the minimum of each symmetric pair. This will no longer be a linear operation, as choosing the minimum pixel value is non-linear, so it is unclear how this will affect convergence.    If we can make this work, combining the new symmetry operator with monotonicity might eliminate the need to use a sparsity constraint, which is advantageous as [~<USER> and I are realizing that sparsity is a wilder beast than it first appeared to be, and taming it is not a simple task. This is because the sparsity of an image is dependent on the total flux in the image, and the brightness of each source, so it might be that using sparsity would require each source in a blend to have a different sparsity requirement dependent on it's brightness, which could be a difficult scheme to implement. Taking care of this directly using a better symmetry constraint is preferable."
Answer: 5563.0

User story: "The range of phase value should be [0, 2)    plotly based phase folding chart doesn't react properly while an invalid period value is selected from the periodogram table. The phase folded chart should show empty content when an invalid period value is selected. "
Answer: 18380.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: "Monitor is a better name for what is currently being called the 'regression' app. In this ticket we will do the renaming which is the first step for using the monitor app  for the Key Performance Metrics measurements and for measurements done by other packages like {{jointcal}}.    "
Answer: 5698.0

User story: Write psuedocode implementations of especially {{define_quanta}} for SuperTasks involved in coaddition.  Verify that that these can be used to build the "Science DAG" either forwards or backwards.  Determine requirements on interfaces relate data IDs via metadata registries, and sketch out one or more APIs for providing them.
Answer: 24425.0

User story: People are starting to use lsst-texmf for document writing but there is some confusion. This ticket is to write a document explaining how to use the lsst latex classes.    The consensus is that this document should match the LSST "software guide" standard and be written using sphinx in a subdirectory of lsst-texmf (rather than writing it in Latex). The documentation will be published to https://lsst-texmf.lsst.io and will include links to the rendered example PDFs.    This ticket covers the writing of the guide. Publishing will be handled separately.
Answer: 7056.0

User story: Following discussions at SuperTask WG meeting I want to start designing new quanta-based interface for SuperTask and Activator. Also want to explore how "composite" SuperTask could look like to be usable by activator (and how it could be constructed.
Answer: 65393.0

User story: "obs_ctio0m9 looks in the wrong HDU for data. Config parameter just needs to be changed from 1 to 0."
Answer: 7069.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: Currently, the approved way of adding bibliography to latex is to use the {{gaia_aa}} style and for DocuShare documents to be in style "LiveLink". This is confusing to people who have no idea the origin of the latex styles.    This ticket will:    * Rename the style file (keeping the old one around for a while for compatibility with current documents).  * Add {{@DocuShare}} bibliography entry and switch the entries in {{lsst.bib}} to use it.
Answer: 4983.0

User story: "The convergence of our new algorithms, SDMM and GLMM are unknown as of now, so we should study the convergence rates of both algorithms (and compare them to the ordinary ADMM) to understand convergence in all three algorithms."
Answer: 659.0

User story: "Currently, the overscan region is defined by the cameraGeom. This ticket is to add the ability to optionally use the header information to define the overscan region for ctio0m9 data.    The functionality is pretty general, and should probably be moved it into obs_base at some point, but this ticket is just to implement a (likely quite hacky) way of doing it for obs_ctio0m9 data."
Answer: 811799.0

User story: "github3.py branch protection API is out-of-date with the GitHub API v3.    A working API that supports strict, enforce_admins and include_admins is required to implement DM-9847."
Answer: 8752.0

User story: "The current unit tests for the DCR template generation prototype uses `numpy.save()` and `numpy.load()` to persist and depersist test data. This format is fragile and has already been broken once with the conversion from swig to pybind11, so a more robust test data format should be used."
Answer: 9841.0

User story: "Create jupyterhub/lab environment atop container release."
Answer: 6960.0

User story: On reviewing DMS-REQ-0274, [~<USER> no longer thinks that "all previous DIASource records corresponding to the object" is correct. Now that DPDD states that we only do characterization for 12 months of history, it makes sense for the alert to only include 12 months as well. Fixing this will require edits to DMS-REQ-0274 in LSE-61 and the alert packet description in LSE-163.
Answer: 37212.0

User story: "Process the RC dataset using the stack version that the full S17B HSC reprocessing will be based on.  Presumably this version will be effectively the same or comparable to the version HSC chooses for their internal data processing. "
Answer: 38911.0

User story: "Some of the HSC RC dataset were not included in HSC-PDR1/DM-9683/{{/datasets/hsc/raw/ssp_pdr1}} although some of them are publicly available.    Obtain them from NAOJ if possible, so to allow processing the exactly same RC dataset and   facilitate QA. "
Answer: 17372.0

User story: "  Fill in the outline made in January ..  "
Answer: 120126.0

User story: "Install and test the LSST Service Abstraction Layer (SAL) and SDK."
Answer: 36132.0

User story: "LDM TCT text is different from LSE CCB text."
Answer: 69.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Write functions that can be used to read and write AFW tables from/to a mysql database.     Auth can be out of band, i.e. rely on a config file on the user's computer."
Answer: 325669.0

User story: "Planning activities for May:  * Began constructing a prototype IT configuration management database (CMDB), including developing the schema as tuples and populating with service dependencies across the Data Facility.  * Prepared for and attended DMLT face-to-face meeting in Seattle.  * Preparation for next cycle plan, including:  ** Near-term storage use cases and proposed improvements to filesystem organization.  ** Improved specification of containerized application management operational model and near-term technical work.  ** Current status of metadata and provenance models and mechanisms.  ** Specification of header writing device, including clarification on data sources, contact, and mechanisms for retrieving metadata information.  * Clarification of process for shipping equipment to Chile.  * Participation in Chilean ITC Tiger Team.  "
Answer: 82279.0

User story: "* Assisted project to prepare replan status presentation for AMCL meeting. Reviewed ITC staffing profile with ICI management.  * Reviewed current ITC and planned deployments, including FY17 network-based security in Chile with storage and systems groups. Coordinate staff transition.  * Resource provisioning and management — Conducted “interviews” with each DM development group to gather resource management needs (notes from each interview are here: XXXX). Discussions about elastic provisioning for master provisioning enclave.   * Worked with network group to identify UIUC-Chicago network architecture, and infrastructure costs and peering fees associated with each PoP in Chicago.  * Rework sizing model to derive pre-operations capacity needs, working from use cases of engineering data plans, calibration plans, commissioning observing programs, and expected pipelines, to calculate both raw data (engineering data, calibration data, commissioning observing programs, etc.) and derived data volumes. This work is ongoing and will be extended to cover the entire survey operations and post-operations.  * Two-day face-to-face meeting with new DM project manager to review replan, discuss documentation and prep for the DM review.  "
Answer: 35866.0

User story: "Bucket ticket to cover non-specific SuperTask collaboration activities."
Answer: 78706.0

User story: "Adds DM-10105."
Answer: 1259.0

User story: "Upgrade starlink_ast to version 8.5.1 in order to gain full support for Chebyshev polynomials."
Answer: 60.0