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: "It would be beneficial to have in the TABLE_NEW_LOADED payload a  trigger field, which would differentiate actions triggered by sort (where  data do not change, only their order) or filter from other loads. We don't  need to reload table statistics or histogram on sort. But we do need to to  reload them on filter.      created TABLE_SORT action to distinguish sorting from filtering.  sorting should not reload xyplot nor catalog overlay.    Also:  - disable history when in api mode.  - ensure tableMeta.source reflects the file on the server.  - fix TablePanelOptions not resetting columns selection.  - remove 'Fits Data' tab when no images available.  - fix 'Coverage' appearing when it should."
Answer: 43640.0

User story: "When new table data received, the related chart data should be updated only for the components on display. Hidden components' data should be lazily updated when a component becomes visible."
Answer: 85257.0

User story: "Review of services (compute, storage, networking) by LSST project before considering work final."
Answer: 73654.0

User story: "Initial draft of the design based on the requirements"
Answer: 302420.0

User story: "Derive requirements from use cases"
Answer: 302423.0

User story: "Review with stakeholders (target users, release manager, others as necessary) to confirm that capability fulfills original requirements. "
Answer: 73675.0

User story: "Review of capability by site security team"
Answer: 73677.0

User story: "Review that design was implemented successfully including recover and supporting documentation exists."
Answer: 73679.0

User story: "Document each component sufficient enough for transfer of knowledge and system recovery as needed."
Answer: 46185.0

User story: "Testing/practicing recovery of node/image/software after various types of faults."
Answer: 33530.0

User story: "OS + updates installation, imaging building, stateless/stateful node provisioning, test of image, security configurations, networking bandwidth tuning, file system tuning, file system installation and tuning."
Answer: 23208.0

User story: "Investigate the overall performance of the application and improve it where possible.  It is pointed out that triview is especially slow compare to expanded.  Need to investigate."
Answer: 8413.0

User story: "In the course of merging DM-4801, the timing was off and there was a change to the deblender code while the stack demo was being updated to use the deblender, so the outputs are slightly off. This ticket should regenerate the outputs with the latest deblender changes"
Answer: 4119.0

User story: "The PS1 3pi PV3 catalog has been released to the PS1 Science Consortium, and will soon be released generally.  Convert the PS1 DVO catalog into the new LSST reference catalog format, and provide a script that can be used to convert this format into astrometry.net format."
Answer: 388671.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: "Monocam is being used on a telescope, and we want to reduce the data obtained.  This is made difficult by the fact that the camera and the telescope are not talking to each other so the usual header keywords are in separate files from the data."
Answer: 14199.0

User story: "Replace side-effects with saga and clean-up chart related controllers (TableStats, XYPlot and Histogram)."
Answer: 4424.0

User story: "Next scripts doesn't stop cleanly MySQL if configuration step fails:    {code:bash}  admin/templates/configuration/tmp/configure/scisql.sh  admin/templates/configuration/tmp/configure/tools/sql-loader.sh  {code}"
Answer: 1893057.0

User story: (1) {{testOutputs}} fails because paths are compared literally  Jenkins run-rebuild #139 failed with pipe_base  https://ci.lsst.codes/job/run-rebuild/139//console  {code:java}  FAIL: testOutputs (__main__.ArgumentParserTestCase)  Test output directories, specified in different ways  ----------------------------------------------------------------------  Traceback (most recent call last):    File "tests/testArgumentParser.py", line 497, in testOutputs      self.assertEqual(args.input, DataPath)  AssertionError: '/nfs/home/lsstsw/stack/Linux64/obs_test/2016_01.0-3-gafa6dd0+10/data/input' != '/home/lsstsw/stack/Linux64/obs_test/2016_01.0-3-gafa6dd0+10/data/input'  {code}    Please make the comparison more robust.     (2) File descriptor leaks  Jenkins run-rebuild #138 failed with pipe_base  https://ci.lsst.codes/job/run-rebuild/138//console  {code:java}  FAIL: testFileDescriptorLeaks (lsst.utils.tests.MemoryTestCase)  ----------------------------------------------------------------------  Traceback (most recent call last):    File "/home/lsstsw/stack/Linux64/utils/2016_01.0-2-g97a6e33/python/lsst/utils/tests.py", line 133, in testFileDescriptorLeaks      self.fail("Failed to close %d files" % len(diff))  AssertionError: Failed to close 1 files  {code}    {code:java}  File open: /nfs/home/lsstsw/build/pipe_base/.nfs000000000a20a3f700005679  {code}  This test passes on local disk.  
Answer: 7341.0

User story: "Create and deploy Beats for Logstash and Elasticsearch. These beats are used to transport logs and monitoring data to ELK.    See: https://www.elastic.co/products/beats"
Answer: 39699.0

User story: "When a significant feature has been added to the code, it should be announced via community.lsst.org and documented in the release notes for the next major version.  Add this to the developer workflow documentation."
Answer: 31590.0

User story: "Now that DM-5561 explains how to migrate to pytest compatibility the developer guide must be updated to state how to use pytest in unittests."
Answer: 41493.0

User story: "Removal of boost smart pointers in DM-5879 missed some meas extensions which are not built as part of {{lsst_distrib}}. Namely: {{meas_extensions_shapeHSM}}, {{meas_extensions_simpleShape}} and {{meas_extensions_photometryKron}}.  Update these too."
Answer: 1227.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> is working with some suprimecam data for an asteroid detection project, and in attempting to run it through the stack we found numerous small bugs that blocked processing. Most of this is normal bitrot since the suprimecam side of obs_subaru (apparently) hasn't been heavily exercised lately. I've compiled a set of minimal changes required to get these data through processCcd.py. Since I only have one set of images with the old MIT detectors, I haven't attempted to generalize these fixes beyond what I could test (e.g., to the Hamamatsu-specific code/configs). "
Answer: 13172.0

User story: "Discussions and planning for allocating the 1PB storage increase within Nebula between object storage and block storage. Further discussions with LSST DM interested stakeholders about this feature. Policy development for use and monitoring of use of this feature."
Answer: 80663.0

User story: "Discussions and planning for the creation of an LSST service-only tenant for better isolation (hence protection) from ad hoc services. Further discussions with LSST DM interested stakeholders about this feature. Policy development for use and monitoring of use of this feature."
Answer: 80664.0

User story: "This activity is outside of LSST project; this story is a placeholder for demonstrating progression toward completion of the epic.    Some activities that are likely to occur:  Software installation, OS installation/updates, RAID configurations, software configuration, monitoring and notification system(s) installation and configuration, integration testing and friendly uses evaluation. "
Answer: 40513.0

User story: "Discussions with vendors. Quote selection. Budget tracking. Quote submission to finance. GCO follow up questions. OBFS follow up questions. Finance follow up questions. Overall tracking of purchase progression."
Answer: 53267.0

User story: "Working with SUI/QServ teams to create a plan that includes deployment schedules, levels of support, discussions of administrative requirements in integration environment, detailed documentation before procurement, security reviews, reviews with deployment team."
Answer: 40542.0

User story: "Feedback/discussions plus revisions. "
Answer: 309469.0

User story: "Create a virtual machine with functioning LSST Software Stack to have an environment where I can see and play with its code."
Answer: 4.0

User story: "Videos from the [DM Boot Camp|https://community.lsst.org/t/dm-boot-camp-announcement/249] cover a lot of topics a newbie like me is interested in."
Answer: 16.0

User story: "Running pyflakes on obs_subaru revels many places where the code is not (LSST specific) PEP8 compliment. Actual coding bugs reviled by pyflakes were fixed in DM-5474, however many of the formatting issues need to be fixed. Once DM-4740 and DM-4668 are done, all remaining code should be brought into coding standard compliance."
Answer: 1933058.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Per request on HipChat, developers would like git-lfs to be available in the shared stack on {{lsst-dev}} and other shared infrastructure.    It's the work of a few seconds to add it: put the binary in {{Linux64/git_lfs/<version>/bin}}, add a trivial table file like  {code}  envPrepend(PATH, ${PRODUCT_DIR}/bin)  {code}  and declare it like  {code}  eups declare -r Linux64/git_lfs/<version> gif_lfs <version>  eups declare -c git_lfs <version>  {code}    It would be even better, though, if this were done automatically by the shared stack maintenance scripts."
Answer: 1864540.0

User story: "This ticket will implement a plot from validate_drp in the QA Dashboard as a proof-of-concept for how existing matplotlib plots can be re-implemented in Bokeh with data from the QA database.    Stretch goals (maybe for a future ticket) will be to overplot the validate_drp output of one job against another’s to understand performance changes."
Answer: 336753.0

User story: "An interesting use-case for the metric time series plots is to compare how one branch compares to another. This would be help developers understand how their code changes affect algorithmic performance before causing a regression on master. This ticket will add the ability to filter and distinguish jobs corresponding to different git refs in the metric time series plot."
Answer: 1886426.0

User story: "The Level 0 QA DB should know what Stack Git refs correspond to each job. This will enable plots to filter jobs based on development ticket so that a developer can understand how a branch compares to master.    This ticket will add jobs to the schema (http://sqr-009.lsst.io/en/latest/#level-0-qa) and create the necessary migration script."
Answer: 21344.0

User story: "Create a (relatively) secure way to use Elasticsearch from outside of Nebula using Ansible. See:    https://www.elastic.co/blog/playing-http-tricks-nginx    Note that this will not allow another Elasticsearch to join but will allow the usual admin and client queries using basic auth."
Answer: 486802.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: "- remove all of the gwt code except for a few remaining files.  - create separate build for the new firefly viewer, leaving the old fftools as it was before the JS conversion.  - repackage files as needed moving forward."
Answer: 9874.0

User story: "See https://docs.fastly.com/guides/securing-communications/allowing-only-tls-connections-to-your-site"
Answer: 503.0

User story: "Once RFC-178 is adopted Astropy needs to be packaged in an EUPS container. Given the complexity of Astropy dependencies the packaging will be done as for {{numpy}} and {{scipy}} by checking that Astropy is available (v1.1 will be the minimum version)."
Answer: 2799.0

User story: "Once RFC-178 is adopted the developer guide has to be updated to include guidance as to how Astropy can be used in the stack (similar to how Boost is documented)."
Answer: 11176.0

User story: "jointcal has its own custom star selector. This should be removed and replaced with a star selector based on meas_algorithms.starSelector. A good choice might be meas_algorithms.objectSizeStarSelector."
Answer: 96319.0

User story: "The Lupton reinterpretation of the ZOGY algorithm in real-space is essentially a post-convolution that implements noise whitening (or decorrelation) of the image difference. We will make a first-pass at implementing this in the existing diffim codebase in order to perform future evaluations on real data."
Answer: 66057.0

User story: "Develop a (1-D?) simple toy model and test the effects of the correction for varying I1 and I2 noise levels and different image PSFs and matching kernel(s). This will be done first in an ipython notebook.    See DM-5914."
Answer: 44373.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 starting a new instance, occasionally something strange seems to happen with the  network setup.  The instance will come up but is inaccessible (icmp, ssh). When this happens, the console log shows that a DHCP address was obtained and cloud-init injected ssh-keys, so it isn't a total network setup failure.    I have seen this happen a few times in the last couple of weeks but I can't reliably reproduce it.  I'm wondering if neutron is logging anything interesting when this happens.    This failure mode happened  again a few minutes ago with 7adffa82-7221-454c-acfe-5f21cdd34ea8.  Which I killed and recreated as instance b6f64981-099b-46e5-a27e-e3694372f447 with the same private IP address.   The new instance is accessible as expected."
Answer: 1031069.0

User story: "There is an initial implementation of fringe correction in the obs_subaru package.  It should be ported and generalized."
Answer: 830774.0

User story: "Overscan correction can be improved.  Specifically, some systems have sharp discontinuities in the bias section."
Answer: 74752.0

User story: "Currently, if a region of sky is simulated in StarFast the stars must always have the same x,y coordinates (before DCR effects). This ticket is to support arbitrary rotations and offsets of the simulated stars to mimic realistic repeated observations of the same field."
Answer: 1851.0

User story: "As part of overhauling XYTransform we will likely need to replace the way we describe the transformations supported by camera geometry and {{Detector}}. This is likely to include a new way of describing the coordinate frames (e.g. {{PIXEL}}. {{FOCAL_PLANE}} and {{PUPIL}}).    If we adopt AST (as seems likely) then these frames will be AST {{Frames}}, the transforms will be AST {{Mappings}} and the collection described by {{Camera}} and {{Detector}} will be one or more AST {{FrameSets}}.    An RFC for the redesigned API for camera geometry will be required and this ticket is to implement the resulting design."
Answer: 702885.0

User story: "In order to evaluate DCR correction algorithms we need a metric that defines the severity of DCR in a residual image. This ticket is to run the new dipole measurement task on simulated difference images affected by DCR, and to define a useful metric. The result will be a brief technical note defining the process and the metric, with a few examples."
Answer: 44512.0

User story: "To use AST in the stack, we need to be clear what our different transformations (AST:Mappings) and endpoints (AST:Frames) are going to be so we can create the chain of transformations (AST:FrameSets) that will be used throughout the stack. This applies to both images and CameraGeom. We may want to produce similar descriptions for other stack objects.    This ticket is the high-level Frames equivalent to the mathematical Mapping description in DM-5918.    This will help us determine how we can put our current input/output image frames into the new system."
Answer: 96367.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 order to use AST in the stack, we may need to add mappings to it. We also need to be able to describe our transforms at a high level so that we know how to create them.    We need a list of the currently necessary transformations (e.g. from afw:wcs, XYTransform, GTransfo and any other relevant stack packages), and some concrete ideas about the kinds of transforms we may need in the future. These should be described in a high-level mathematical manner, independent of our wcs/transform system.    This can be informed by DMTN-005 and the requirements section of DMTN-010"
Answer: 35996.0

User story: "We need to design a new API for the WCS/Transform system. This is somewhat independent of the question of how the low-level code is used: we want a clean and simple API that lets the components of the stack create, manipulate, use, and persist the necessary transformations. Related to this question is whether we will still need skyToPixel/pixelToSky or whether the necessary operations with those can be subsumed into some Frame-to-Frame transformation (e.g. pixel-to-pixel or tan-to-tan).    The product is an RFC"
Answer: 227525.0

User story: "We want to better connect our other transforms with the WCS system, which means reworking the guts of XYTransform to work with AST. This could involve making one or both of them a wrapper, complete replacement, or writing a converter that turns our transform object into an AST map or FrameSet.    The product is a design"
Answer: 308044.0

User story: "Following the to-be-written recommendation for DM-4157, we plan to rework the guts of afw:Wcs to use AST. We need to decide how afw:Wcs will use AST, whether as a wrapper or as a complete replacement with AST.    The product is a design"
Answer: 307835.0

User story: "Develop a better understanding of the planned implementation of ZOGY in real space by implementing the kernel correction in k-space and investigating its characteristics when transformed back into real space. Do this either symbolically (if possible) or numerically in an ipython notebook. First in 1-D, then in 2-D, both assuming a constant kernel. Include documentation in the ipython notebook describing the current understanding of how this will be implemented"
Answer: 29981.0

User story: "Give the workers the ability to move user queries to the everything scan if they are taking too long to complete a Task or several Tasks."
Answer: 128193.0

User story: "Add a low priority ScanScheduler to the worker to handle very slow scans or scans that do not  work well on the other schedulers."
Answer: 96564.0

User story: "The czar needs code to limit the number of Tasks sending back large results at any given time."
Answer: 40022.0

User story: "When large results are returned from the worker to the czar, the thread should leave the thread pool and the Task should indicate to the scheduler that it is done.   "
Answer: 25946.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "There are times when it is desirable for a thread to continue but effectively leave the thread pool and be considered finished by the scheduler. util::ThreadPool needs to modified to do this."
Answer: 17267.0

User story: "ScanScheduler is using heaps to order Tasks by chunkId. This makes it difficult to add Tasks to actively running chunks, which causes a significant delay to the start of query execution. Using a list of buckets of Tasks where each bucket is for one chunkId will make it easy to add Tasks to chunks being. Within each bucket it will still be necessary to order Tasks by tables used in the query."
Answer: 69145.0

User story: "Remove the qmeta::QueryId and use the typedef of QueryId in global/intTypes.h instead. Also try to verify that QueryId is used instead of uint64_t where applicable."
Answer: 69160.0

User story: "In DM-3368, we stripped out the focus calculation since it's not camera-generic, and the scatter/gather isn't necessary for general processing.  We need to reinstate the focus calculation in its own scatter/gather script."
Answer: 145374.0

User story: "In the review of DM-5447 we decided it made sense for [~<USER> to take over finishing the technote, in particular providing an introduction and concluion with more context."
Answer: 267981.0

User story: "LTD Keeper needs to purge Fastly when an Edition is rebuilt. Currently the surrogate-key for the build is also used to cover editions. This means that the key needed to purge an edition is the same as that for an build. Hence purging an edition means that the system needs to purge the surrogate key of the previous build.    We're seeing situations where the surrogate key that Keeper is purging is not the one that needs to be purged. A more robust configuration would be for each edition to have a stable surrogate-key that can be unambiguously purged.    This ticket covers the following work:    # Diagnose the issue.  # Enable Alembic migrations for Flask (Flask-Migrate)  # Add a surrogate-key column to the Edition model  # Change the S3 copy rebuild code to change the surrogate-key header  # Change the rebuild code to purge based on the edition's surrogate-key."
Answer: 9095.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: "obs_decam currently uses a {{%(path)s\[%(ccdnum)d\]}} template for its calibs (bias, dark, flat, fringe).  This is desirable in order to support calibs provided from external sources (e.g., NOAO).  However, our calib construction code does not support such a path ({{path}} cannot be inferred for new data, and we can't write MEFs from multiple processes).  We believe the best path forward is to split the {{DecamMapper}} into two mappers, one supporting calibs from external sources and one supporting calibs we construct ourselves.  The alternative is to copy the external calibs to match a template like {{BIAS/%(date)s/BIAS-%(date)s-%(ccdnum)02d.fits}}, which means breaking apart the MEFs.    I suggest also moving the defects into the obs_decam package because they're required for use, small and we don't have code to regenerate them."
Answer: 162217.0

User story: "If a user browsers {{example.lsst.io/v/}} or {{example.lsst.io/builds/}} we should present a dashboard that dynamically lists available editions and recent builds, respectively.    This could be implemented as a React app that interacts with the public LTD Keeper API. Thanks to Fastly we could serve a single app for all documentation products, and customize the dashboard according to the URL."
Answer: 705603.0

User story: "Currently if a user browses {{example.lsst.io/v/main/some-directory}} instead of {{example.lsst.io/v/main/some-directory}} they will receive an error.    We should develop a scheme where Fastly can detect that such a path is a directory and redirect to the directory's index.html page."
Answer: 130992.0

User story: Previously we deployed documentation on Read the Docs. By default, Read the Docs would show the master version of documentation on "/en/latest/". Many links with that endpoint may already exist. We should configure Fastly to redirect such paths to "/".
Answer: 6950.0

User story: "LTD Keeper's database resides on a Google Compute Engine Persistent disk attached to a Pod. We need to develop automated backups of this DB within a Kubernetes microservices architecture.    A possible solution is a lightweight pod that periodically runs a backup task that copies the DB to S3. A backup retention policy would also need to be considered."
Answer: 138163.0

User story: "We need to log LTD Keeper to Panopticon in order to understand the service's operations and diagnose issues.    Note: this ticket may need to be refactored into two parts    1. Building the logging adapter from a Kubernetes Pod to Logstash  2. Implementation of logging inside the Keeper codebase.    Related links:    * http://www.structlog.org/en/stable/ for formatting logs in Python  * https://hynek.me/articles/taking-some-pain-out-of-python-logging/  * https://hynek.me/talks/beyond-grep/"
Answer: 858324.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 should add {{\-Wno\-unused\-local\-typedefs}} to our gcc options.  This cleans up the build significantly, because there's a flood of warnings of this type coming from boost.  If we suppress those, it might become possible to notice warnings that we care about."
Answer: 9090.0

User story: "Several pages in the Developer Guide either name leadership positions in DM (i.e., Project Engineer, etc) and/or the people who have those role. Recently DM's leadership organization changed but these documents were not updated. The following pages should be updated to reflect both the correct people, and the correct roles (e.g., the Project Engineer roles does not exist).    - http://developer.lsst.io/en/latest/processes/code_of_conduct.html  - http://developer.lsst.io/en/latest/processes/decision_process.html"
Answer: 368066.0

User story: "The {{--print-fail}} flag appears to broken for at least some failure modes.    https://github.com/lsst-sqre/buildbot-scripts/blob/master/lsstswBuild.sh#L145    Eg.    https://ci.lsst.codes/job/stack-os-matrix/label=centos-6/10673//console"
Answer: 924738.0

User story: Create a JSON or YAML file with:    - Qserv version  - libraries/deps version  - other idea welcome    This will interesting "GROUP BY" in monitoring tool (performance for each Qserv or xrootd version for example)
Answer: 31626.0

User story: "A MySQL account needs to be created in configuration procedure and on existing data on IN2P3 cluster in order to enable ELK access. MySQL password/secret has to be shared accross all containers."
Answer: 27330.0

User story: "obs_decam originally included 'object' and 'proposal' fields in the registry but these were removed at some point.  Putting them back would allow users to more easily select data.    I also suggest surveying the headers for additional useful fields."
Answer: 503411.0

User story: "Now that DM-5771 is closed and processCcd runs again, get back to the point where the things are not just not crashing but are actually working correctly (given that this is a non-standard use-case)."
Answer: 269415.0

User story: "Consider use of Boost in the stack, and investigate where it can be eliminated by using std library equivalents. Create tickets to remove it, then work on them."
Answer: 51422.0

User story: "Replace all use of Boost smart pointers through the stack with their standard library equivalents.    This will require an RFC."
Answer: 10069.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 issue has several components; I'm combining them into a single issue because they need to be done atomically:   - Rewrite the base_ClassificationExtendedness SingleFramePlugin/ForcedPlugin as an AfterburnerPlugin (and remove the old versions).   - Move the "applyApCorr" subtask out of SingleFrameMeasurementTask and ForcedMeasurementTask, making it instead a subclass of their parent Tasks.   - Add afterburner subtask stages to ProcessCcdTask (within DetectAndMeasureTask) and the multiband tasks wherever measurement is currently being run.  The afterburner tasks should be run after aperture corrections are measured and/or applied.    After these changes, throughout the stack, whenever a MeasurementTask is run, we also run ApplyApCorrTask and AfterburnerTask (in that order), while possibly running MeasureApCorrTask immediately after the MeasurementTask.    This may or may not enable significant cleanups in DetectAndMeasureTask (I haven't looked closely).  If so, they should be done on this issue.    Given all the moving parts, it's important to check that the actual behavior of the pipeline (in the aperture correction and extendedness values) does not change, so it might be useful to start by creating some reference outputs to compare against.
Answer: 99379.0

User story: The [Developer Guide|http://developer.lsst.io/en/latest/processes/decision_process.html#role-of-the-assignee-in-reaching-consensus] tells us:    {quote}  When consensus is established, and a set of implementation tickets is created, the Assignee is responsible for marking the RFC as Adopted in JIRA.    Once the RFC is adopted, the Assignee should create tickets that implement the implementation plan.  {quote}    This seems to imply that we create one set of implementation tickets before hitting "adopted", and another set afterwards. I'm sure that isn't the intention. Please clarify.  
Answer: 1462.0

User story: "Write a paragraph or two describing alternatives to the constrained bulge+disk model currently in the DPDD."
Answer: 22854.0

User story: "[~<USER> has requested a description of the different flavors of coadds, and the tradeoffs between the more experimental optimal coadds and the non-optimal standard ones.    I'll try to do this as both a presentation for the DMLT and a DMTN (with essentially the same content).    This will include a bit of toy-model simulation work to try to predict some of the tradeoffs; this could make the discussion quite a bit more quantitative and I have an idea for how to do it that is pretty easy."
Answer: 49245.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: "Some CCD cameras can have delays between when the reset a chip and when they read it, during which time dark current accumulates. [~<USER> discovered that DECam has header keywords to describe exactly this situation:  {quote}  EXPTIME 10.0  DARK TIME 11.09515  {quote}    We need to handle this;  I'm not sure if the LSST camera will have this issue, but other cameras we process will.  One issue is where the information comes from;  it's presumably going to be in the headers, but before we can use it in the pipelines it needs to be unpacked into an object, and it isn't obvious which one (Calib isn't quite right)."
Answer: 1460587.0

User story: The existing diffim implementation in the stack defaults to the (2000) version of the Alard/Lupton algorithm. Other recent improvements such as "pre-convolution", delta-function basis, model selection via BIC, others, seem to be implemented but are not turned on. We need a good understanding of the existing implementation so we can assess how straightforward it is to implement the ZOGY algorithm in real-space in the stack.
Answer: 52979.0

User story: We need to get a good understanding of where the image subtraction implementation in the stack currently stands. This first requires an up-to-date assessment of the literature, including Becker et al. (2012), and ZOGY (2016). Also, the "preconvolution" step.
Answer: 40088.0

User story: "Try to use {{lsst.log}} instead of {{lsst.pex.logging}} for a few science pipeline tasks, based on log {{u/ktlim/getLogger}} branch and DM-3532. Look into RFC-29."
Answer: 8698.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Here's some tracks:    1. Run multinode integration tests during qserv_distrib CI build.  In order to do that we could create a qserv_testmultinodes repository containing a build script which would launch multinode tests (for example see travis.yml)  I can do this on my side but i'll require a recent version of Docker on the build machine.    2. I'll need your help to do next step:  Each time command below succeed:  {code:bash}  rebuild qserv_distrib  {code}  publish this build to eups web repository and docker hub by running:  {code:bash}  # bXXX is the build id and is available at the bottom of rebuild command standard output  publish -b bXXX -t qserv-dev qserv_distrib  # then create and publish to docker hub image "qserv/qserv:dev"  # which embed current build products and is used for all Qserv deployment  # (bare-metal, openstack, travis, developper machines)  $QSERV_DIR/admin/tools/docker/2_build-dev-image.sh  {code}    As a TODO list, here's what could be done in an additional ticket, in the long term:    - run multinode integration test inside Jenkins instead of Travis?    * Travis/Gitub integration is very good, so I'm not sure this feature is still an active concern?    * on the other hand Travis has to download qserv/qserv:dev at each build, and if there's a timeout here, the build sometime fails. I don't know if this image can be cached in Travis free version?    * current procedure doesn't support yet tickets branch accross multiple repositories, (like qserv+xrootd+qserv_testdata for example). Do you think this feature would be easier to implement in Jenkins?
Answer: 1894690.0

User story: "Make a package to hold the description of moncam."
Answer: 22048.0

User story: "- Added arrow up/down to move between rows.  - Added page up/down to move between pages.    - Fixed table loading mask not showing  - Fixed PagingBar rendering more than it should  - Fixed annoying StandardView missing unique key warning"
Answer: 199.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 class FileFluxCmdJson in VisServerCommand.java is calling   {code}              String[] res = VisServerOps.getFileFlux(fahAry, pt);  {code}    However, when the mouse is outside the image, the VisServerOps.getFileFlux(fahAry, pt) returns:  {code}  new String[]{PlotState.NO_CONTEXT}  {code}  It is fine for a single band.  However, for 2 or 3 bands, the for loop below caused the index out of bound error because res is an array of length=1 and the expected res is an array of length=no of bands.  {code}    JSONObject obj= new JSONObject();              obj.put("JSON", true);              obj.put("success", true);                int cnt=0;              JSONObject data= new JSONObject();              for(Band b : state.getBands()) {                  data.put(b.toString(), res[cnt++]);              }              data.put("success", true);  {code}    Thus,  res\[cnt++\] caused array index out of bound error.     To fix this issue, the for loop is changed as below:  {code}                        int cnt=0;              JSONObject data= new JSONObject();              Band[] bands = state.getBands();              for (int i=0; i<res.length; i++){                  data.put(bands[i].toString(), res[i]);              }              data.put("success", true);                JSONArray wrapperAry= new JSONArray();              obj.put("data", data);              wrapperAry.add(obj);  {code}    When the mouse is outside the image, the res returns a new String\[\]\{PlotState.NO_CONTEXT\}, it is added to the JSONObject only once.  
Answer: 8244.0

User story: "Ginga and Glue (glueviz) are community visualization tools in Python. Become familiar with the capabilities of both, thinking from the point of view of using Firefly for the display but using Python for many other things."
Answer: 40231.0

User story: "In preparation for linking Jupyter notebooks with Firefly and other SUIT components, read Jupyter documentation. Learn how to build a sample widget or interactive dashboard in the Jupyter framework"
Answer: 136636.0

User story: "Add a qa server + rds instance to the terraform configuration for the jenkins-demo sandbox for development purposes.  It may make sense to split this off to be an independent sandbox but that is very easy to do, if needed."
Answer: 33053.0

User story: "Currently, [with some difficulty] it is possible to discover the {{user_id}} that created an instance (might be possible for other resources as well) but it is not possible to map this back to a username / person.  This can make it difficult to 'self police' instances.    The administrative API endpoints are not publicly accessible and I doubt any end user has the appropriate permission. "
Answer: 1135949.0

User story: "The LSST project is currently at 81/100 instances but there are over 200 cores unused.  Is it possible to increase the instance limit or are we being encouraged to use large instance flavors?"
Answer: 15883.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 appears that at some point in the last few months the horizon console interface has stopped working.  I am still able to access the console log output via the API/CLI."
Answer: 1043976.0

User story: "When generating 3-color image, the label for the image display should 'Project 3-color', i.e.   WISE 3-color, 2MASS 3-color ...  "
Answer: 7017.0

User story: Please provide a minimal level of documentation for {{pipe_drivers}}, to include:    * A {{doc}} directory with the usual content so that docstrings get generated by Doxygen;  * A package overview;  * All docstrings should be appropriate for parsing by Doxygen (ie, should start with {{"""!}} where necessary).
Answer: 24592.0

User story: "Get three hosts in NCSA nebular system to deploy the current Firefly application. The goal is workout the possible issues and identify the software needed to be installed for the hosts. Clarify which team is responsible to install what third-party software packages."
Answer: 1510598.0

User story: "Prepare a draft schedule, with some detail for 2016-2017, for deployments of the SUIT into (test) production, including the datasets that will be served."
Answer: 64967.0

User story: "Prepare functional and quantitative requirements and the SUIT-centric elements of design for the planned Fall 2016 SUIT deployments (SDSS Stripe 82 and WISE)."
Answer: 65087.0

User story: "Prepare initial set of SysML diagrams of the SUIT's relationship to other system components."
Answer: 824100.0

User story: "go through the original requirement of SUIT,  put them in the categories:  done, Tier1, Tier2    "
Answer: 135454.0

User story: "Document the flowdown of Level 3-related requirements from SRD, LSR, OSS, and DMSR."
Answer: 1013850.0

User story: "Create an outline of the sections of the Level 3 ConOps document"
Answer: 1107707.0

User story: Continue the work described in DM-5301 through the standard "multi-band" coadd processing workflow.    Performing an end-to-end comparison of the stacks will not be possible until {{meas_mosaic}} is fully operational on LSST (DM-2674). However, until that point is reached, comparisons are still possible by either:    * Shepherding data through {{meas_mosaic}} and coaddition on HSC, then performing further processing and measurement using the LSST stack;  * Omitting {{meas_mosaic}} from the workflow altogether and performing end-to-end comparisons of the stacks without mosaicking.    Obviously, neither of these will ultimately be adequate, but they should enable early identification of any major issues.
Answer: 57162.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 currently provide some guidelines on ["best practices" for commit messages|http://developer.lsst.io/en/latest/processes/workflow.html#git-commit-message-best-practices] in the development workflow documentation.    However, we also provide a document on ["Git Setup and Best Practices"|http://developer.lsst.io/en/latest/tools/git_setup.html], which makes no reference to the above guidelines.    It would be helpful to ensure that all our guidelines for git usage are available from the same location.    (It would be even better if we could be clear about what's a requirement and what's a suggestion...)
Answer: 4121.0

User story: "I propose:    1. Create {{testdata_lsstSim}}.  This will be based on 12 images from the current Twinkles Run 1 (or pre-Run 1):  2 epochs each of 6 filters.  (/)    2. Add an optional test method to {{obs_lsstSim}} that runs if {{testdata_lsstSim}} has been declared.  This is the way these tests are set up for the other {{obs_*}} packages.    3. Add {{testdata_lsstSim}} dependency to {{lsst_ci}} (which already depends on {{obs_lsstSim}}).    This will then be run every time a full standard default Jenkins build is processed."
Answer: 1476177.0

User story: "The CoordSys.js defined ECL_B1950 incorrectly.  When I was testing WebGrid, the grid lines for  Ecliptic B1950 were not right.  Looked further, it was caused by wrong equinox value in its definition."
Answer: 10441.0

User story: "There are some issues with three color when not using all three bands (i.e. using on green and blue):  * Mouse readout is not labeled correctly  * FITS head popup does not come up    Other FITS header popup issues:  * If file size is too big then the text is wrapping  * On safari, the resizable indicator in on every cell  "
Answer: 13245.0

User story: "Increase the loading and processing speed of {{validate_drp}} following suggestions by [~price]    1. Don't read in footprints  Pass {{flags=lsst.afw.table.SOURCE_IO_NO_FOOTPRINTS}} to {{butler.get}}    2. Work on speed of calculation of RMS and other expensive quantities.  Current suggestions:  a. {{calcRmsDistances}}  b. {{multiMatch}}  c. {{matchVisitComputeDistance}}  d. Consider boolean indexing in {{afw}}'s {{multiMatch.py}}  {code}     objById = {record.get(self.objectKey): record for record in self.reference}  to:     objById = dict(zip(self.reference[self.objectKey], self.reference))  {code}    Note that while this ticket will involve work to reduce the memory footprint of the processing, it will not cover work to re-architect things to enable efficient processing beyond the memory on one node."
Answer: 445383.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 a discussion in the Tea Time HipChat room today, this is a "note to ourselves" to take a look at the behavior of Firefly when visualizing images with negative flux values.    This is important for difference imaging and is therefore highly relevant to both LSST and ZTF (if ZTF difference images become visible through Firefly at some point).    The behavior of the asinh stretch, in particular, should be looked at.
Answer: 1353152.0

User story: "A couple recent changes to the stack break imageDifferenceTask.     Requires updates to only a few lines.     While I'm updating it to reflect the star selector API, I'm also changing the default star selector from SecondMoment to ObjectSizeStarSelector (which I learned today is what the stack has been using by default for a while). "
Answer: 1087.0

User story: "Per discussion in HSC telecon 2016-04-19."
Answer: 11186.0

User story: "See: https://github.com/lsst-sqre/ltd-keeper/blob/master/app/route53.py#L157    This same code works with my own AWS account and credentials - using one of my own domains.    My AWS account has been in a weird state since it was created. I also don't have permissions all over the place in the management console and can't use IAM."
Answer: 1245.0

User story: "Add a paging bar similar to the one for table to the ImageMetaDataToolbarView.  This pages images instead of rows."
Answer: 8591.0

User story: "Improve the star/galaxy separation for validate_drp.    Many of the LSST SRD KPMs are defined for bright, isolated stars.  There is clear evidence that galaxies are being included in current runs (they have significantly higher photometric scatter at the same mag|SNR).  Improved star/galaxy separation will help generate better numbers    Stretch goal:  Include additional informative plots about how well the `extendedness` value in the catalogs is successfully separating stars and galaxies."
Answer: 1510940.0

User story: "Parameters are not sent to the server when requests are posted via fetchUrl."
Answer: 4308.0

User story: "When building mariadbclient, cmake identifies libz from a separate python installation than the one setup to run the stack. I have an anaconda installation on the disk, and a miniconda installation set up specifically for the lsst stack. During the building process CMake for some reason finds the alternate libz associated with that python installation."
Answer: 72081.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 {{SdssShape}} contains a number of poorly-motivated numerical constants ("magic numbers", e.g. [here|https://github.com/lsst/meas_base/blame/master/src/SdssShape.cc#L241]) and inconsistent sanity checks (compare [here| https://github.com/lsst/meas_base/blob/master/src/SdssShape.cc#L96] and [here| https://github.com/lsst/meas_base/blob/master/src/SdssShape.cc#L440]).    Please audit the code for these issues. In particular:    * Check for numerical constants and ensure their values are appropriate and properly justified.  * Ensure that checks on the shape determinant are consistent, including both those listed above and those added in DM-3935.
Answer: 1846436.0

User story: "Should convert GWT's logic over to TabPanel.  - shrink title as needed.  - show full title on mouse over"
Answer: 8905.0

User story: "in DM-2634, the Asinh stretch algorithm  was implemented, but the behavior was not quite right. We need to figure out the issue and make it right. One possibility is that the understanding the relationship  of zero point  and black point, maximum point and white point. "
Answer: 61634.0

User story: "The design of the indexed reference catalogs requires a butler to be sent to the loader.  This requires passing the butler down through the chain of subtasks from the parent command line task.  In this case, I believe only calibrateTask constructs sub-tasks that requires a reference catalog.    This will also require moving the loader and indexer to meas_astrom, otherwise it will introduce a circular dependency."
Answer: 62138.0

User story: "Document the math role and directive available in Sphinx in the ReStructuredText Style Guide section of the DM Developer Guide."
Answer: 1.0

User story: "This will give user finer control of turning on/off the catalog overlays on one image, a group of images, or all the displayed images. "
Answer: 739008.0

User story: "* convert the make support from GWT  * Make a temporary dialog to control it  * Add python/JS API supporty"
Answer: 170286.0

User story: "For now this is the artifacts for WISE images.   We should look at the possibilities to generalize this. "
Answer: 750270.0

User story: "The {{run}} method in the {{PhotoCalTask}} has an argument that selects whether to use the extendedness parameter to select objects for photometric calibration.  This is a good idea, but it should be configurable, I think. "
Answer: 7193.0

User story: "Jean Coupon has requested support for SGE in ctrl_pool."
Answer: 1970631.0