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

User story: "Currently standard procedure to deal with segfaults is to run a debugger. While this works for developers it is inconvenient for end users and potentially impossible for intermittent bugs on large clusters.  Hence automatically printing a backtrace on segfault can be useful to quickly diagnose problems.  A quick trial implementation suggests that relatively easy, this ticket aims to add this functionally to the stack."
Answer: 13041.0

User story: "Familiarise yourself with the written outputs of the SuperTask WG, including:    - The PR resulting from DM-10600;  - Pages on Confluence to be provided by [~<USER>."
Answer: 93570.0

User story: "Make sure there are no overwhelming community objections to the design & requirements outlined in DMTN-043"
Answer: 10071.0

User story: Missing features include:  - specifying multiple SuperTasks on command line  - loading Pipeline from serialized format  - support for "show" command    Multi-task support may need rethinking of UI for command line.
Answer: 36153.0

User story: "`eimageIsr.py` in `obs_lsstSim` imports functions from `ip_isr` with `from lsst.ip.isr import isr`, but this only imports functions inside `isr.cc`. This import statement should be changed to `import lsst.ip.isr as isr` for the rest of the code in the module to work."
Answer: 2808.0

User story: Furusawa-san writes:  {quote}  I have determined the color terms for the new 3 narrow bands for PS1  bands. I feel like I would like to update only the 3 bands for now not  to destroy things in the other bands in this last minute change.  Do you agree with this idea? Or should we update all the other bands  as well for consistency?  {code}  'N387': ColortermConfig.fromValues("g", "r",  0.549932112641, 1.93524092848, 0.335209939226), # fit to GS83 at g-r=(-1, 1.25)  'N718': ColortermConfig.fromValues("i", "r", -0.0374215790806, -0.293620763883, 0.190069559821),  # fit to GS83 at g-r=(-1, 2)  'N973': ColortermConfig.fromValues("y", "z", -0.0064016547183, -0.0391528142634, -0.240885647814), # fit to GS83 at g-r=(-1.5, 0.5)  {code}  altenatives  {code}  'N718': ColortermConfig.fromValues("r", "i", -0.0374215792408, -0.706379236521, 0.190069560819),  # fit to GS83 at g-r=(-1, 2)  'N973': ColortermConfig.fromValues("z", "i", 0.0126946008687, 0.282064376721, -0.0636499458066), # fit to GS83 at g-r=(-3, 3)  {code}  {quote}
Answer: 216.0

User story: "The concept will be implemented as as an option in Firefly, so that it can be reviewed in Firefly CCB and improved, if needed.     Put multi-trace charts into tri-view. This ticket should also include handling Charts dropdown and default plot.   "
Answer: 191534.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 need to migrate Firefly Histogram (with the bind calculated on the server) to multi-trace chart architecture. This includes options and table connections.     Since histogram parameters do not map exactly to Plotly bar chart attributes (we use variable width bars to represent bins), this would be a good addition to the multi-trace charts proof-of concept.    Other items that should be resolved by this ticket   - Separating firefly specific things from plotly trace data  - Not storing fetchData function in tablesource, it's preferable to store a string id that can be resolved into this function  "
Answer: 19002.0

User story: "Currently, our multi-trace charts create a new plot on EVERY update. We need to to use Plotly's restyle and relayout to speed the updates like highlight change, changing style, adding/removing errors, etc.    Ideally, we'd like to calculate and handle the changes in PlotlyWrapper.  This is a very important issue to be resolved BEFORE we can start using multi-trace charts in tri-view."
Answer: 33350.0

User story: "Arrange for, order, and receive small-scale Dell loaner systems for initial testing."
Answer: 1.0

User story: "[~<USER> and I have been working on a paper to publish the GLMM algorithm that we developed as part of the deblender. This ticket exists to create a more simplistic example than the deblender (hyperspectral imaging) for the paper."
Answer: 79560.0

User story: "Jointcal does some odd things when building its RefStar catalog ({{Associations::collectRefStars}}), including creating fake errors (maybe because the original reference catalogs didn't have useful errors?), making a magnitude from the flux (is that really necessary? Why can't we work in flux units here?), and making {{BaseStars}} followed by a cast, when it should just be able to make {{RefStars}}."
Answer: 1007568.0

User story: Demonstrate that both the BFD and Metacalibration codes can run to existing interfaces by making direct coadds with a CoaddPsf and ignoring covariance. As such, this will be the first "full" experimental run, but we expect the results to be poor.
Answer: 81705.0

User story: "Towards the end of the epic, after multiple rounds of experiment, define the final set of simulation parameters that will be used to produce the ultimate result.    This is likely the culmination of multiple rounds of iteration with gradually increasing complexity."
Answer: 346152.0

User story: "The simulation code we'll be using for DM-10579 has been provided by Erin; ensure that it's possible to interface it with the BFD codebase."
Answer: 81132.0

User story: "Is Galsim a viable option for propagating uncertainty, or do we need to write something bespoke for this purpose?    If the latter, file a new ticket to do that work."
Answer: 80517.0

User story: "In {{afw::fits::writeImage}} continuity is only guaranteed for {{ndims == 2}}, fix this."
Answer: 4369.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: "Design document proposal for the Header Clients. This will include Data Source and data types. Assembly methods and communications with DDS. "
Answer: 499489.0

User story: "Per discussion at the May 2017 DMLT F2F (and prior to that), we need to clarify the status of EUPS. Is our relationship to it broadly the same as to any other external project (Boost, SCons, etc), or is it something we should allocate effort to supporting in house? If the latter, should that effort be from the existing maintainers or from SQuaRE? Currently, neither group has it in their plan."
Answer: 1758504.0

User story: "Update DMTN-044 to reflect the acceptance of the SQuaRE provided binary release system, and that decisions about long-term release maintenance will be deferred until the release manager position has been filled, and place it in Docushare."
Answer: 27156.0

User story: "The lablauncher interface is still rapidly evolving.  Each time there's a new release there's a need to do some tweaking to accomodate changes."
Answer: 60458.0

User story: "Create a new release of LTD Mason with the version of ruamel.yaml pinned to prevent future version incompatibilities.    See https://github.com/lsst-sqre/ltd-mason/pull/5 :    bq. There will be API changes in the 0.15+ versions, that might lead to warnings that your users could see. Therefore please release a version of your package with this change, so that it will not automatically take the latest ruamel.yaml release."
Answer: 131.0

User story: "Furusawa-san writes:  {quote}  ccd=43 has also been affected by the glowing corner since 2016-04-01 UT, and better to be treated.  Is it possible for us the include the mask for ccd=43 as well?  A possible suggestion is as follows:    Since 2016.4.1:    #CCD x0    y0    width height  43    0   0     512   200  43    0   0       70 4176  {quote}"
Answer: 79.0

User story: "This ticket will de-couple the REST interface, and potentially the VO API layer as well, from ImgServ Core, which will then become a library, thus enabling greater flexibility for change the web front ends while providing scalability to handle service requests. After completion, be able to perform a simple VO operation:  is service available? "
Answer: 118060.0

User story: "Use ImageMapReduce to implement a spatially-varying A&L decorrelation task. Integrate that task as an option in imageDifference.py.    Will possibly want to implement it as a subclass of ImagePsfMatchTask, because that task includes wrapper code for warping, which will be necessary here."
Answer: 124862.0

User story: "Use ImageMapReduce to implement a spatially-varying A&L decorrelation task. Integrate that task as an option in imageDifference.py."
Answer: 20039.0

User story: "The current code for generating the grid upon which to split exposures to perform spatially-varying operations is unnecessarily complex and has some bugs. For this story, we will fix that code and test it on real data."
Answer: 9981.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: "{{exposureFromImage}} in meas_base assumes that an object with a {{getVariance}} method is a {{MaskedImage}}; this is no longer true as of afw commit 29f62c6f25    Please fix this; pybind11 makes it possible to use {{isinstance(image, afwImage.MaskedImage)}} for this test.    "
Answer: 4144.0

User story: "DM-9751 created a new source selector that inherits from matcherSourceSelector called matcherPessimisticSourceSelector. This source selector is a stop gap measure to preserve the behavior of matcherSourceSelector for matchOptimisticB. If the new matchPessimisticB is adopted from a future RFC as the default matcher this ticket will merge the two source selectors and matcherSourceSelector with take on the behavior of matcherPessimisticSourceSelector."
Answer: 971779.0

User story: "We have the first set of SUIT requirements. They need to be part of the science platform requirements. "
Answer: 97831.0

User story: "Outline and prioritize components required for end-to-end testing of L1 alert generation--most immediately to enable verify_ap development (DM-9676 and others)."
Answer: 27575.0

User story: "At the May 2017 DMLT Face-to-Face I agreed to formally capture the WCS requirements in DMTN-10 (plus any free-floating in [~<USER>'s mind)."
Answer: 1008772.0

User story: "Change logging setup to use shovel-based RMQ transport for logstash."
Answer: 222.0

User story: "The shipping rate that is currently in the model reflects a cost of shipping equipment directly from NCSA to Chile. In practice this is not how shipping is handled. Updating to reflect shipping costs from NCSA to Tucson, from Tucson to Chile as well as expected shipping insurance charges"
Answer: 130973.0

User story: "Survey year column was pushed back one year too far. This column was supposed to describe the year in which we would buy the equipment for the following survey year. Survey year one will be in 2023, so we have survey year now marked in 2022 to show purchases happening in 2022 for the survey in the following year. Storage Requirements and Compute Requirements have also been corrected to be in line with this "
Answer: 2.0

User story: "Verify what inputs are generating the rack counts for floorspace costs, wanting to validate that what size the racks are and verify that they are at the capacity needed. Rack and PDU costs were also not currently reflected in the model and those costs have been added. "
Answer: 368768.0

User story: "Review storage input numbers to increase accuracy of tech predictions. For example, current model states 24 drives per tray when current technology supports 60 drives per tray and soon will be 84"
Answer: 368770.0

User story: "Discussed costing of networking (Ethernet, Infiniband, and WAN) to correct costing to current technologies and project needs. Looking into WAN costs to determine accurate split of costs that will be incurred Getting updated quotes for the Ethernet costs, and removed the Infiniband costs"
Answer: 368773.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: {{SafeClipAssembleCoaddTask}} can use more than 17 GB per process in coadding 200 images, with a 6000x6000 patch size. This is excessive, as the coaddition doesn't use more than 5 GB. I suspect it's in the clipping, and may be due to memory fragmentation from serially reading in images and creating masks.    {code}  pprice@lsst-dev01:/scratch/pprice/desc $  $ export TIMEFORMAT="      Time spent in user mode   : %U sec      Time spent in kernel mode : %S sec      Total time                : %R sec      CPU utilisation           : %P%%      Max resident set size     : %M Kb"  pprice@lsst-dev01:/scratch/pprice/desc $ /bin/time -f "$TIMEFORMAT" assembleCoadd.py /scratch/pprice/desc/REPO --rerun test --configfile assembleCoadd-config.py --selectId filter=r --id filter=r patch=7,7 tract=0 --doraise --no-versions |& tee assembleCoadd.log  [...]      Time spent in user mode   : 48584.29 sec      Time spent in kernel mode : 3265.03 sec      Total time                : 235331271 sec      CPU utilisation           : 77%%      Max resident set size     : 17675816 Kb  {code}
Answer: 645310.0

User story: "We're running production with bright star masks, so those should also be in the integration test. Otherwise there's the possibility that production fails when ci_hsc passes."
Answer: 17387.0

User story: Define metrics that will help determine health and status of the alert production MVP. The deliverable of this story is a list of all the metrics which are expected to be tracked in the first version of the MVP (the "minimal minimum").
Answer: 139240.0

User story: "By the All Hands Meeting, we should be able to demonstrate verification metrics by reporting running times (wall-clock) for AP pipeline stages. This ticket covers writing code for applying the {{verify}} framework to inline tests, profiling each stage, and supporting SQuaSH export (though the export itself is the responsibility of {{verify_ap}}).    See DM-11118 for a list of pipeline stages. This ticket may report metrics at a finer-grained level than is presented there."
Answer: 130859.0

User story: "Please add metadata access for {{Filter}} objects via the same pattern used to implement {{DM-9060}}.  I hope this is essentially trivial."
Answer: 18667.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: "Jointcal's improved photometric fit is done on the full focal plane, and thus we need its persisted output to be able to convert pixel coordinates on one CCD to the focal plane. Probably the easiest way to implement this is to create an {{astBoundedField}} that we can put into a {{PhotoCalib}}.    We may eventually want to replace {{PhotoCalib}}'s use of {{BoundedField}} internally with AST, but for consistency with [~<USER>'s {{meas_mosaic}} work, keeping the {{PhotoCalib}} interface the same is probably best.    For reference, jointcal's photometric output looks something like {{f(g(x,y))*h(x,y)}}, where {{(x,y)}} are in pixel coordinates, {{g}} is the pixel to focal plane transformation, {{f}} is a Chebyshev polynomial, and {{h}} is some chip-level transform (currently a constant).    Tagging this PairCoding, as it might be nice for me to sit with [~<USER> as he works on it, to aid my familiarity with AST."
Answer: 55892.0

User story: "Draft and submit addendum to contract to cover transfer of NCSA inventory to Aura/Chile."
Answer: 10343.0

User story: "A fatal TaskError in CmdLineTasks does not return a non-zero exit code unless {{--doraise}} is specified. For example, this command (taken from DM-10755) failed with a TaskError from   [here|https://github.com/lsst/meas_base/blob/1d674c83109bb665bc2ad102ea0c2f737f99197b/python/lsst/meas/base/references.py#L226] and can be reproduced on lsst-dev:    {code:java}  forcedPhotCcd.py /datasets/hsc/repo --rerun DM-10404/WIDE:private/username/xxx --id ccd=100 visit=32254  {code}      This gave an exit code of 0.  If {{--doraise}} is added to the command line, it gave 1.  The stack {{w_2017_17}} was used.      This seems very relevant to DM-4141, or arguably duplicate, although that ticket seemed to focus on the precall part."
Answer: 10254.0

User story: "DM-8491 added some code that enumerated warpTypes as enum.Enums.  This third party package is not an official dependency. Backing that out. "
Answer: 1275.0

User story: "The generic DAX generator, _Daxgen_ and _Executor_ reached the level of maturity allowing to prepare and perform a validation test showing that an arbitrary workflow persisted in a generic format (e.g. GraphML) can be run successfully."
Answer: 215.0

User story: "Participate in discussion at the International Virtual Observatory Alliance northern interoperability meeting in Shanghai, primarily focused around community readiness to be on the receiving end of LSST's alert system (mainly Time Domain Interest Group, but also working groups like Data Model, Data Access Layer, Grid and Web Services, Operations, etc.)    Meeting website:  http://ivoa2017shanghai.csp.escience.cn/dct/page/1    Programme:  http://wiki.ivoa.net/twiki/bin/view/IVOA/InterOpMay2017    "
Answer: 117.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Create some docker files and directories to act as a starting point for a firefly docker environment.    Remove the ups and tomcat directory from the repository.  This as there to provide a way to distribute firefly but using Docker will be a much better way."
Answer: 21560.0

User story: "{{TransformMap}} can transform a point between two coordinate systems that are not its reference coordinate system (but are related to it), but it cannot create an {{XYTransform}} that maps two such coordinate systems.    I understand {{TransformMap}} may soon operate on {{afw.geom.Transform}} rather than {{afw.geom.XYTransform}}, and that {{TransformMap}} itself may be replaced by another class.  I think the same feature should be supported after those changes (and possibly before, depending on when we get to this issue)."
Answer: 1656.0

User story: "Initial fits of donuts with the donut pipeline appear to indicate that optical distortion needs to be either removed from donut images before fitting, or included in the forward model.  This is corroborated by communication with Euclid and LSST PSF experts.  This ticket is to add a constant (per donut) optical distortion Jacobian to the forward model using the nominal afwCameraGeom transformations."
Answer: 37657.0

User story: Furusawa-san points out that "pipe_drivers" isn't in the packages provenance list. I believe this is because the {{\_\_init\_\_.py}} doesn't {{from .versions import *}}, so there's no version information to grab.    I should survey other packages as well, and/or make a workaround in the code that saves the versions.
Answer: 8657.0

User story: Furusawa-san notes that we need to "accept NB0718 (not NB0716) & NB0973 bands for CHORUS processing."
Answer: 244.0

User story: "Test the corrections made in {{meas_mosaic}} in DM-10688 by running a full HSC-RC run with the current stack to see if the ellipticity residuals are better."
Answer: 10704.0

User story: "Preparation for the framework review presentation 2017-05-31."
Answer: 281.0

User story: "As the batch production service using Pegasus is being prototyped, documentation of the individual packages are not enough as they do not provide a bigger picture. The goal is to create a centralized place (a technote) to document current design of the service which eventually will evolved it the complete description of it."
Answer: 12.0

User story: "This ticket documents data preparation and loading for the following WISE catalogs:  || Catalog name || PDAC database || PDAC table || IRSA download page ||  | WISE All-Sky Single Exposure (L1b) Source Table |  wise_4band_00 | allsky_4band_p1bs_psd | http://irsa.ipac.caltech.edu/data/download/wise-4band-psd/ |  | WISE 3-Band Cryo Single Exposure (L1b) Source Table | wise_3band_00 | allsky_3band_p1bs_psd | http://irsa.ipac.caltech.edu/data/download/wise-3band-psd/ |  | WISE Post-Cryo Single Exposure (L1b) Source Table | wise_2band_00 | allsky_2band_p1bs_psd | http://irsa.ipac.caltech.edu/data/download/wise-2band-psd/ |"
Answer: 251983.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: "Design think/whiteboard time on data distribution and replication system"
Answer: 3.0

User story: "DM-2186 broke meas_mosaic (not surprising since it isn't in CI), and it looks like the right fix is to move the configuration that makes us use the new reference catalogs instead of astrometry.net into meas_mosaic itself, since there's no point having an override in obs_subaru when only obs_subaru uses meas_mosaic.  "
Answer: 4056.0

User story: There is a need to be able to choose from and save to user workspaces so a result of a catalog search of millions of rows are not saved into local disk and re-upload to the server as different search input.    This story is about developing 2 components:  - File picker that will be connected to user workspace and will replace the system default file finder  - Workspace 'manager' which will let the user manage the files such as rename, delete, move. (the component should allow more action to be developed and added in the future such as "Open with" or "send to" or "share with" for example). This component could be integrated in the tool or exposed as standalone app.    The underlying server and workspace code should be kept as generic as possible, so other protocol could be added on top in such a way that we would switch from protocol to another.     Currently, only webdav and VOSpace have been mentioned but it shouldn't be a limit for the server side to allow adding others in the future without having to refactor (too much) the code.  
Answer: 790196.0

User story: Initial pipeline prototype supports only single-task "pipelines", mostly for the reason that command line parser does not know how to parse multiple task names. We want to have support for specifying multiple tasks, I can imagine several options for that:  - multiple task names on command line, each task needs specification of the configuration overrides  - loading pre-defined serialized Pipeline from a file, that will contain everything including configurations  - (my newest idea) loading pipeline from a "specification file" directly avoiding serialization of Pipeline, "specification" can be some sort of DSL or maybe pure Python script.    For each of the above cases we need command line support of course. Some extension of a Pipeline concept/interface related to Pipeline construction is likely needed too.
Answer: 735564.0

User story: "During May hack week we built initial prototype of the command line framework which is just a big blob of code with minimal separation of concerns. It is time now to refactor that and separate reusable components which can be used by other implementations.    This should go into F17 cycle (there is no epic yet defined for F17 supertask work)"
Answer: 33077.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: "Specialization of the foreman device into multiple devices - one of which is a prompt processing device. The NCSA Foreman must be brought in line with these changes. The return of result sets must be added to the NCSA foreman. The NCSA foreman needs methods added for contacting the Condor Cluster to ask for resource availability, provide file location info, and collecting results."
Answer: 3.0

User story: "Splitting the base foreman into multiple devices requires the addition of supplementary queues and new messaging glossary entries. This is not a trivial refactor, but moves base code beyond the prototype stage."
Answer: 1.0

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

User story: "When running meas_mosaic with the pybind11 wrappers the detector coordinates were not being updated. This resulted in the incorrect wcs solutions being written to disk."
Answer: 8929.0

User story: <USER>writes:  {quote}  I found that RingsSkyMap.findAllTracts() behaves oddly at poles.    The docstring of RingsSkyMap.findAllTracts(self, coord) says it returns a list:  https://github.com/lsst/skymap/blob/master/python/lsst/skymap/ringsSkyMap.py    When coord is IcrsCoord((0, -90), degrees), however, findAllTracts() returns not a list but a TractInfo. (line 163).    When coord is IcrsCoord((0, 90), degrees), it raises an error because line 166 "return self[-1]" is wrong. It has to be "return self[len(self)-1]".  {quote}
Answer: 4545.0

User story: "Based on the slurm statistics collected during the processing or anything post-mortem, summarize the computing resource used in DM-10404. "
Answer: 107925.0

User story: "This ticket exists to coordinate work on developing the first version of the LSST Science Platform Vision Document.    The most recent version of the document can [be found by following this link|https://github.com/lsst-dmsst/lsst_science_platform/blob/master/science-platform.pdf]."
Answer: 190624.0

User story: "This ticket exists to coordinate work on [May 2017 DMLT F2F|https://confluence.lsstcorp.org/display/DM/DM+Leadership+Team+Meeting+2017-05-09+to+11%2C+Face-to-Face] action:    {quote}Science Leads: provide prioritized list of requirements to Wil O'Mullane, work with T/CAMs to ensure the expressed priorities are consistent with the plan.{quote}  "
Answer: 157692.0

User story: "Document the use of Python 3 in DM integration and testing plans."
Answer: 161238.0

User story: "Building upon DM-10588, create a Docker image that comes pre-installed with lsst-texmf (and a fully texlive distribution from DM-10588).    This Docker image can be used by projects that don't include lsst-texmf as a submodule."
Answer: 8545.0

User story: "Create cookiecutter templates for LSST LaTeX documentation projects. Like https://github.com/lsst-sqre/lsst-technote-bootstrap but for LaTeX documents.    The cookiecutter templates should be embedded in the lsst-texmf project."
Answer: 10031.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Create an inventory of content in Doxygen (prose content; not API references) to support planning of how to port and refactor this content into pipelines.lsst.io. This ticket won't cover porting itself.    Additionally, inventory the Bootcamp tutorials: https://community.lsst.org/t/dm-boot-camp-announcement/249?u=<USER>
Answer: 28937.0

User story: "This ticket covers creating a Getting Started tutorial for pipelines.lsst.io. The aim is to let a person who has never used the pipelines have a hands-on experience with the Stack to understand its patterns and capabilities and develop good feelings for it.    The best route is to adapt content from https://dmtn-023.lsst.io:    - Rework as a tutorial, with deeper explanations moved to framework processing context docs.  - Update the tutorial so that it works."
Answer: 88150.0

User story: "Work on the stack installation guide at https://pipelines.lsst.io with two goals:    - Update for v14 and document the binary release.  - Improve the usability of our installation documentation."
Answer: 217840.0

User story: "The timeout in {{CmdLineTask}} catches a lot of people unawares, and causes lots of confusion and annoyance. It's necessary (because of that python {{multiprocessing}} bug) to have _some_ value, but as soon as we stick a value in people manage to exceed it. [~<USER> had a good idea: we make the value a number _per target_, which will make it harder to exceed when people throw lots of data at {{-j}}. That just means calling {{getTargetList}} a bit earlier."
Answer: 10470.0

User story: "Under some restricted situation, we may allow users to be able to access the file system directly.   "
Answer: 995501.0

User story: "_Executor_ can work in two modes. It can either use existing input repository or create one from scratch in a specified location. Currently, when in latter mode, by default, it deletes any directory in that location before starting building a new one. The mode is selected automatically based on presence certain fields in job description. It may lead to accidental removal of an existing dataset repository if a malformed job description file is used. The goal is to make _Executor_ much more careful when dealing with existing dataset repositories and  remove anything only if explicitly asked."
Answer: 6916.0

User story: "The verify package works successfully in both Python 2.7 and 3.5 with lsstsw on my own Mac. however it fails on Jenkins with errors related to metric parsing (log attached). This ticket tracks those issues down."
Answer: 607.0

User story: "This ticket will implement RFC-341, creating a new script for registering (but not linking/moving) calib files into a repository. The default behavior for {{ingestCalibs.py}} will then be to both register and move/link files."
Answer: 87996.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: "Following DM-8686 (between tagged weeklies {{w_2017_11}} and {{w_2017_12}}), the {{constructBias.py}} (etc.) scripts in pipe_drivers write their outputs in the output storage rather than in the calib storage (e.g., {{/tigress/pprice/ci_hsc/DATA/rerun/ci_hsc/BIAS/2017-12-34/NONE/BIAS-2017-12-34-012.fits}} instead of {{/tigress/pprice/ci_hsc/DATA/rerun/ci_hsc/CALIB/BIAS/2017-12-34/NONE/BIAS-2017-12-34-012.fits}}).    This appears to be due to the output repo being unaware of calibs because it's not being told about them by the {{ArgumentParser}} in pipe_base.    This was originally reported by Furusawa-san at NAOJ."
Answer: 42.0

User story: "Do an initial investigation into docker and understand a basics on how Firefly would be deployed with it."
Answer: 1452.0

User story: "Following the plan made in DM-10045, make an example demonstration of the type of plots we will want for interactive QA plotting.  Implement data computations to mirror the current structure of the {{pipe_analysis}} plotting code, in order to simplify the future process of porting more of its functionality into Bokeh."
Answer: 69266.0

User story: "_Executor_'s documentation is slightly out of sync with the code due to its implementation of logging capabilities. The goal is to update it by describing how to use them."
Answer: 222.0

User story: "In contrast to the regular pybind11 type casters the ndarray ones don't work well with {{nullptr}}.  E.g. the function {{void testOptionalArray(ndarray::Array<double, 1, 1> * arr = nullptr)}} should accept {{None}} as a default argument, but it does not."
Answer: 22019.0

User story: "The current deblending scheme uses the same constraints on each peak. It will be useful to allow different constraints to be used for each peak so that (for example) sparsity can be different for each source or a garbage collection object can be created that does not have monotonicity and symmetry constraints."
Answer: 80687.0

User story: "The current PSF operator in the new deblender uses the PSF for the image in each band to attempt to deconvolve the image to a single pixel. This appears to be causing issues with deblending the wings of faint extended objects that are not seen when using PSF-matched images and no PSF operator (see attachments for an example).    It is thought that convolving the image in each band to a common PSF (such as the best seeing)  will remove the artifacts that the current PSF convolution operator produces."
Answer: 485575.0

User story: "It is likely that objects like spiral galaxies with a resolve bulge and disk or extended galaxies with color gradients will prove difficult for a single SED deblender. This ticket will test using multiple SEDs for a single peak on HSC data to see if it is able to deblended more complicated structures."
Answer: 168961.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: When using images not convolved with the PSF, we've long known that "snowflakes" or spiky fractal-like structures are created due to the monotonicity operator. It is likely that a smoothness operator, which is used in compressive sensing applications, will be able to fix (or at least suppress) this problem.
Answer: 454066.0

User story: "The current deblender uses an update scheme similar to ADMM, where constraints are not strictly enforced in any given step but instead the solution converges to meet the constraint. It should be possible to make monotonicity a proximal operator applied to the likelihood gradient, as opposed to a linear constraint, which will force a strict monotonic solution.    This ticket will be an attempt to add the option of using strict monotonicity in the deblender."
Answer: 8606.0

User story: "{{SpanSet::intersectNot(SpanSet)}} uses nested for loops iterating over the two sets, O(N^2). It would be much more efficient (O(N)) to have a coordinated iteration (so long as the sets are sorted).  {{SpanSet::intersectNot(Mask<T>, T)}} currently creates a new {{SpanSet}} from the mask, and then creates another {{SpanSet}} with the overlap. I wonder if it would be more efficient to iterate over the mask with the span and create only one {{SpanSet}} result.  {{SpanSet::_runNormalize}} uses {{std::vector::erase}}, which is rarely a good idea.  "
Answer: 19569.0

User story: "The {{Config}} history recording currently takes about 8% of a ci_hsc run time. This is because every time a Config field value is set or changed, we get a traceback to record the history, and that (apparently) involves checking files, so there's lots of {{stat}} calls.    Try disabling the {{Config}} history recording, and if this results in a significant performance improvement then RFC for approval.    The ability to record {{Config}} history is an important feature which should not be removed completely --- just disable it. An alternative optimisation of the {{Config}} history without disabling it would be welcome."
Answer: 29984.0

User story: "YAML parsing with pyyaml currently takes about 4% of the time of a ci_hsc run. This can be optimised by using libyaml to build pyyaml instead of using the pure python implementation:  * http://pyyaml.org/wiki/PyYAMLDocumentation  * https://stackoverflow.com/questions/27743711/can-i-speedup-yaml"
Answer: 12586.0

User story: "I recently discovered a new means of doing C++ profiling, using tools that should be available on any Linux distro:  {code}  LD_PROFILE=libmeas_modelfit.so LD_PROFILE_OUTPUT=`pwd` measureCoaddSources.py /scratch/pprice/ci_hsc-copy/DATA --rerun ci_hsc --id patch=5,4 tract=0 filter=HSC-I  sprof -p -q libmeas_modelfit.so libmeas_modelfit.so.profile > libmeas_modelfit.so.profile.txt  {code}  This should be documented in the [Developer's Guide under Profiling|https://developer.lsst.io/coding/profiling.html]."
Answer: 1020.0

User story: "Create  an outline for Firefly testing procedure.   Fill in as much content as possible."
Answer: 100691.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "As in DM-9517, many calls to display with DS9 use the old ds9 specific interface.  Change to use the registered display interface, and test to be sure each of the modules displays correctly when its display variables are set to True in debug.py."
Answer: 1155222.0

User story: "Prepare an outline for Science Platform design document"
Answer: 60868.0

User story: "When the result of a user query is too large, it bogs down the system and can crash the czar. When the result of a query on the czar breaks a certain value, the entire query should be cancelled."
Answer: 2920.0

User story: "Add documentation in reStructuredText format to the display_firefly package, in a doc/ subdirectory. The documentation will include setup of the afw.display interface, including the host, port, etc. parameters that are specific to display_firefly. Other points (like known issues) unique to display_firefly will be covered.    display_firefly is not yet included with lsst_apps or lsst_distrib. Initially, an Installation section will be included. It is expected to replace the contents with links to centralized pages on how to install additional packages against a core stack installation.    Copied for pull request  https://github.com/lsst/display_firefly/pull/7  * Add doc/_static placeholder README  * setup initial files following validate_base as template  * add installation, start tutorial  * ignore eupspkg directory  * add setup of display_firefly for Python API ref  * add introduction, installation content  * fill out rest of Using... section  * Pin Sphinx<1.6.0  * Various reStructuredText formatting fixes  * reformat Makefile  * Merge branch 'tickets/DM-11017' into tickets/DM-10601"
Answer: 275506.0

User story: "Yoshihiko Yamada noticed that we aren't including pixel flags in the forced measurements, but they are very useful there especially since the centroids may be different from the unforced measurements."
Answer: 50.0

User story: "Merge calexp and coadd image directory trees from NCSA and IN2P3 sides of the SDSS/Stripe82 processing to match a new version of the merged catalogs in the PDAC database *sdss_stripe82_01*.    The datasets shall be put into these folders:  {code}  /datasets/sdss/preprocessed/dr7/sdss_stripe82_01  /datasets/sdss/preprocessed/dr7/sdss_stripe82_01/calexp  /datasets/sdss/preprocessed/dr7/sdss_stripe82_01/coadd  {code}"
Answer: 1617.0

User story: "ci_hsc is now taking over an hour to run, when it used to take around half an hour. Why?"
Answer: 14103.0

User story: "All coding for SuperTask hack week May 22-26 goes into this bucket."
Answer: 10046.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It can take a while to build a lsst-texmf document on Travis CI. The trouble is that we're installing a full texlive every time. It _might_ be more efficient to download a Docker image with texlive pre-installed and run the latex build from that container.    One question is whether to include lsst-texmf or not with the image. I think it may be wise to create a base image without lsst-texmf since some projects will include lsst-texmf as a submodule. Then a second Docker image, with a Dockerfile in the lsst-texmf project, can layer lsst-texmf upon that."
Answer: 5367.0

User story: QServ throws non-standard MySQL exceptions. mysqlclient/MySQLdb doesn't propagate errors higher than a predefined number, so it returns an error code of -1 with message "Totally whack" The goal of this issue is to propagate the errno and error in that exception.
Answer: 277.0

User story: "Running under Jenkins:  {code}             obs_decam: 13.0-12-ga2ce546+35 ...........................................................................................................................................................................................................................................................................................................ok (638.1 sec).  {code}    I believe this is due to running {{ProcessCcdTask}} within the {{TestCase.setUp}}; it should be in the {{TestCase.\_\_init\_\_}} so it only gets run once."
Answer: 361.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: "Large results are bogging down the czar. The primary problem at the moment appears to be that the qserv process on the czar is using very large amounts of memory for unknown purposes. A user query that has a 5GB result is causing the czar to use about 14GB of memory, which is perplexing. This is approximately per large result user query, so it is easy run out of virtual memory. The memory is eventually released after the query completes and does not otherwise appear to be a leak.     This problem only occurs when the large result code is triggered on several chunks. This happens when results from the chunk do not fit in a single message. qserv tells xrootd ssi to wait before asking for the next set of data for that chunk.    This is perplexing in that the results come back from workers in relatively small pieces that are handed off to the database quickly. Even if they are not being freed, it leaves 9GB of memory use unknown. "
Answer: 147022.0

User story: Obs package needs adjustment so that {{processCcd}} can run properly.    Image assembly, construction of master cals and application of isr was fixed in DM-10253. We now need to get to the point where the rest of {{processCcd}} can run.    We need to deal with the the fact that we only have Ra and Dec in the headers, and manually insert enough information for a nominal wcs to be created, create a {{filterMap}} for the {{refObjLoader}} so that the wacky filters we have here map to _something_ in the reference catalogues, and find out how well that's going to work for matching.    We may also need to create tweaks for the installation of the initial PSF. Early results indicated that some exposures were failing on the number of cosmic ray pixels detected, which was _temporarily_ worked around by upping the allowed number from 10k to 100k, but I suspect (without having looked), that this is happening because the nominal (or measured) PSF is too large, and is causing the spectra (which are long and thin) to be seen as objects sharper than a PSF, and are then flagged as CR pixels. This obviously needs to be fixed.    "Working" astrometry is in quotes as it is not obvious until work has gone further how well we will and should be able to get matches on dispersed images, given the pollution from the spectra. I also don't know where these lie on the sky, and whether they will overlap with the reference catalogs that we have.    Also deal with any number of other mysteries along the way :)
Answer: 60667.0

User story: "Havin xrootd as a microservice would allow to benefit kubernetes high availability when it crashes."
Answer: 96171.0

User story: "Line 49 of https://github.com/lsst/afw/blob/master/src/image/makeWcs.cc should log a warning before returning a None wcs, as it makes it hard to track things down without it."
Answer: 9805.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 reused object aspect of caching (documented in LDM-463 draft) is causing confusion because shared objects can be mutated, and this is not what some developers would expect. Disable it and/or remove the code for now. If it's wanted, we can have an RFC or RFD about how to handle mutable objects.    Also update LDM-463 (remove the bit about caching)  "
Answer: 1200.0

User story: "The butler appears to incorrectly cache images retrieved using a `_sub` variant -- if a different {{BoundingBox}} is specified the old version is used.  For example,  {code}  exp1 = butler.get('calexp_sub', dataId, bbox=bbox1)  exp2 = butler.get('calexp_sub', dataId, bbox=bbox2)  {code}  return an identical portion of the image, even if {{bbox1 != bbox2}}.    Discussion on slack revealed that the {{bbox}} is part of the dataId, but only the part used to look up the data is used when caching.  "
Answer: 6373.0

User story: "In DM-4597 we agreed on a new DM requirement that each data release should include a cross-match table mapping Objects in the current data release to each of the previous data releases. This has now been included in [LCR-962|https://project.lsst.org/groups/ccb/node/1726] and a request has been made to estimate the impact on staff effort in construction, and the sizing model.  "
Answer: 57562.0

User story: "Implement changes to display_firefly to enable it to work with more servers, and fix some issues found in testing.    * Add a {{basedir}} parameter, to make use of the capability added in DM-9843, to allow the firefly backend to be used with the PDAC server and the public IRSA server.  * Pass keyword arguments to the FireflyClient constructor.  * Update the image and mask handling, in part for changes due to the pybind11 conversion, and to restore mask labeling.    In afw.display:    * Fix the \_\_getattr\_\_ method of the display interface  * Reorder tests so that displays are not closed prematurely"
Answer: 18879.0

User story: "We are now developing DM change-controlled documents using latex but we have no documented policy for this or a description of the process. The process is slightly different to code development and involves specific requirements for review and release.    Add a section to the developer guide."
Answer: 279612.0

User story: "Currently, {{dax2graphml}} returns the transpose of the graph representing the workflow."
Answer: 26.0

User story: "Furusawa-san pointed out that coaddDriver can produce outputs even if mosaicking has not been run though {{doApplyUberCal=True}} (which is the default value for HSC). This appears to be due to allowing null values of the {{wcs}} and {{ffp}} in {{updateExposure.py}}.    We should allow the functions in there to fail if the appropriate values are not available, or the user can be deceived as to what corrections have actually been applied."
Answer: 9300.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "As subject, the Doxygen documentation at https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/ returns a 404.    The content does seem to be available at http://doxygen.lsst.codes/stack/doxygen/x_masterDoxyDoc/, but RFC-319 has not been implemented yet. "
Answer: 313669.0

User story: "Plotly does not perform well during resize especially on Firefox.  Make the plotly react component smarter about when to update during resizing and add masking to indicate working."
Answer: 2841.0

User story: "Many clients of {{XYTransform}} use its methods {{linearizeForwardTransform}} and {{linearizeReverseTransform}}. We do not yet have analogous code for {{Transform}}. This functionality can be implemented as either a method on {{Transform}} or a separate function; the latter would provide better encapsulation."
Answer: 44579.0

User story: "This is the most obvious and useful application of RFC-279:   - Add {{image}}, {{mask}}, and {{variance}} properties to {{MaskedImage}} (and {{Exposure}}, for convenience).   - Add a {{maskedImage}} property to {{Exposure}}.   - Add {{array}} properties to {{Image}} and {{Mask}}.    These will cut down on unnecessary characters and save us from having to make temporary variables in order to assign to an image component.  "
Answer: 3199.0

User story: The DPDD tells us that "Level 1 data products are a result of difference image analysis" (§3.1), as opposed to "Level 2 data products [which] result from direct image analysis" (§4.1).    However, this definition is incorrect. Per LSE-29 (which is the highest-level document in which I can find this defined), "Level 1 Data Products [are] the result of processing of the stream of image data from the Data Collection system during the course of normal observing" (LSR-REQ-0033), while "Level 2 Data Products [are] the result of periodic processing of the entire archive of raw image data from the Data Collection system" (LSR-REQ-0036).    This isn't just mindless pedantry: I think there's an important distinction to be made here. A literal reading of the DPDD would suggest that level some 1 data products are generated during an annual data release, while some of the products of nightly processing (e.g. PVIs) are actually level 2. That's inconsistent with usage elsewhere, and I find it actively confusing. Can we fix it, please?
Answer: 1128684.0

User story: "Release LDM-151 as approved by RFC-338.    * Move bib entries to lsst-texmf  * Update change record and release date, remove draft.  * Merge draft to master.  * Upload to DocuShare."
Answer: 5505.0

User story: "In JL container, make stack owned by running user"
Answer: 1768.0