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: "Among SQuaRE and Co. we have an agreement to rename {{validate_base}} to {{verify}} ({{lsst.verify}} Python namespace). This better reflects the definitions of verification and validation. Similarly, the metrics definition package will be renamed to {{verify_metrics}} from {{validate_metrics}}.    Together, these packages form the basis of a new *Verification Framework* that is the pipelines counterpart to the SQUASH server-side infrastructure.    Since {{validate_drp}} relies upon {{validate_base}}, and we need to decouple Verification Framework development from an eventual {{validate_drp}} upgrade, we will keep the {{lsst/validate_base}} GitHub repo, and create a fork called {{lsst-dm/verify}}.    # Create fork in {{lsst-dm}}.  # Rename fork to {{verify}}.  # Merge existing ticket branches being integrated onto {{tickets/DM-8477}} onto {{master}}.  # Change Python namespace in {{verify}} (using this ticket's branch).  # Have GitHub break the fork and move the package to {{lsst/verify}}.  # Add package to lsstsw    Updating {{validate_metrics}} will be easier (and can be competed first}:    # Rename repo to {{lsst/verify_metrics}}  # Change Python namespace (using this ticket's branch)  # Add package to lsstsw    If possible, this migration will be completed before other tickets in this epic are merged so that their diffs make sense in a {{verify}}-context. The rebases should be ok."
Answer: 8948.0

User story: "As per the discussion in RFC-315, two config parameters need to be added to overscanCorrection() to allow excluding the first and last n rows.    Both parameters should default to 0, so that the default configuration reproduces current functionality. "
Answer: 744398.0

User story: "Port the old-style Trac docs for the camera geometry to a new-style DM Tech Note.    https://dev.lsstcorp.org/trac/wiki/Winter2014/Design/CameraGeomDesign  "
Answer: 10497.0

User story: "When I build afw using clang on osx I see the following warnings:  {code}  src/detection/PsfFormatter.cc:68:16: warning: expression with side effects will be evaluated despite being used as an operand to 'typeid' [-Wpotentially-evaluated-expression]      if (typeid(*storage) == typeid(dafPersist::BoostStorage)) {                 ^  src/detection/PsfFormatter.cc:76:21: warning: expression with side effects will be evaluated despite being used as an operand to 'typeid' [-Wpotentially-evaluated-expression]      else if (typeid(*storage) == typeid(dafPersist::XmlStorage)) {                      ^  src/detection/PsfFormatter.cc:91:16: warning: expression with side effects will be evaluated despite being used as an operand to 'typeid' [-Wpotentially-evaluated-expression]      if (typeid(*storage) == typeid(dafPersist::BoostStorage)) {                 ^  src/detection/PsfFormatter.cc:99:21: warning: expression with side effects will be evaluated despite being used as an operand to 'typeid' [-Wpotentially-evaluated-expression]      else if (typeid(*storage) == typeid(dafPersist::XmlStorage)) {  {code}"
Answer: 118530.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 the [DMLT meeting of 2017-04-03|https://confluence.lsstcorp.org/display/DM/DM+Leadership+Team+Meeting+2017-04-03], write a document describing plans for large-scale data processing in support of DRP development goals during F17. It should be available for discussion at the DMLT meeting of 2017-04-10."
Answer: 7184.0

User story: "The {{w_2017_14}} weekly fails to build as part of the shared stack in {{lsst-dev01:/ssd/lsstsw/stack}}. This may be related to segfaults previously reported by [~<USER>."
Answer: 5.0

User story: "Implement RFC-317 by wiping out the shared stack in {{lsst-dev01:/ssd/lsstsw/stack}} (or, perhaps, moving it aside) and creating a new stack in its place.    Take precautions to make sure that the toolchain used to build the new stack is always consistent.    Consider bumping to newer versions of EUPS, Anaconda etc than come by default in the {{shared-stack.py}} script. Also install AstroPy through {{conda}}."
Answer: 7357.0

User story: "Igor would like to make use of the qhttp embeddable C++ HTTP server that was developed during DHT prototyping in some of his own upcoming data distribution prototypes.    This ticket encompasses work to import the qhttp source into the qserv tree, and integrate build of the library and its associated unit tests with the existing qserv scons infrastructure."
Answer: 82519.0

User story: "Gfortran appears to compile in a case-sensitive mode if MAKEFLAGS is set. This causes the build to fail because module files are created with lower case filenames, but are called using capitalized file names."
Answer: 1110.0

User story: "We need to create an Oauth2-based authenticator that relies on a whitelist of a user's organization membership rather than a fixed whitelist, and creates user-appropriate subdirectories if they aren't there, so anyone in LSST can use the jupyterhub implementation."
Answer: 13199.0

User story: "Add unit test asserts to lsst.afw.geom.utils:  - assertSpherePointsAlmosttEqual  - assertSpherePointListsAlmostEqual  - assertPointListsAlmostEqual    and unit tests for them. This work is needed (or at least very useful) for the new WCS classes."
Answer: 3127.0

User story: "With DM-9559 we are able to parse {{specs/}} in {{validate_metrics}}. In doing so, I found some minor formatting issues with jointcal's specifications. This ticket fixes those issues."
Answer: 10475.0

User story: "See RFC-313 and DM-9992  "
Answer: 21438.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In DM-8467, the meas_modelfit dependency of lsst_apps was temporarily removed:    {code}  commit 041ae975d9c60a41b24488ec0ba1768431330fd8  Author: Pim Schellart <<EMAIL>>  Date:   Tue Feb 14 15:51:46 2017 -0500        Disable meas_modelfit until pybind11 wrapped    diff --git a/ups/lsst_apps.table b/ups/lsst_apps.table  index dce8fd4..b239e74 100644  --- a/ups/lsst_apps.table  +++ b/ups/lsst_apps.table  @@ -1,5 +1,6 @@   setupRequired(meas_deblender)  -setupRequired(meas_modelfit)  +# temporarily disable meas_modelfit until pybind11 wrapped  +#setupRequired(meas_modelfit)   setupRequired(pipe_tasks)   setupRequired(obs_lsstSim)   setupRequired(obs_sdss)  {code}    meas_modelfit is now pybind wrapped (DM-8465), so this should be reverted."
Answer: 1286.0

User story: "It looks like significant fraction of the L1DB update time in my current prototype is spent on indexing DIAObject table on each update. I want to test an option to disable night-time indexing and index new data only during daytime.     In practice it means that we need to write to a separate non-indexed table during the night and merge that tablewith actual DIAObject during day housekeeping operations."
Answer: 34334.0

User story: "DM-9952 is merged to master, but I typoed the Jenkins run {{DM-9952}} not {{tickets/DM-9952}} and didn't notice failing tests from afwdata; afwdata is not present on tiger in Princeton where I did my local testing.    This ticket is to capture the errors turned up when I *did* run the tests.    "
Answer: 732.0

User story: "The current deblender uses an alternating least squares algorithm to solve for the SED and Intensity matrices that model each source. The problem with this algorithm is that it fixes the intensity, solves for the SED using SDMM, fixes the SED, solves for intensity using SDMM, etc. until a solution converges (or a maximum number of iterations is reached), meaning that the correlation between the terms is ignored. So while each procedure in isolation is guaranteed to converge, the alternating solution is not, and in some cases does not. The good news is that even a non-convergent solution usually appears to be a good fit, however it takes longer for the algorithm to run.    Boyd 2011 gives an algorithm to solve the NMF problem using ADMM with no constraints, which is an easier system to solve than the current deblender. However, [~<USER> and I believe that we can adapt the algorithm to work with our current multiple linear constraint formalism (SDMM) to both guarantee convergence and assure faster convergence.    Because this is a new algorithm, and likely to be the final major algorithmic change, we have decided to implement this procedure before profiling the code and testing the constraints, as optimal values might change slightly with the new algorithm."
Answer: 34295.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: "validate_base's BlobBase type is currently intended to be an abstract base class that apps create subclasses for. The original intention was that blob data would be computed within the Blob subclass's code.    With the new validate_base we're going towards a composition model with container types. This ticket is to convert BlobBase into a Blob class, and permit applications to store data into the Blob instance through standard mapping idioms."
Answer: 11583.0

User story: "Once the design of {{validate_drp}} (or another more desirable validation framework) is understood, produce a similar design for the {{verify_ap}} product. I will not dictate the format of that design here, but this issue should be resolved by linking to it in some way."
Answer: 126663.0

User story: "After we have a prototype pipeline running for the HiTS data, it would be good to transition that to a more generic framework like the one used in {{validate_drp}}.  This is to review the current design of that package to assess its utility as a blueprint for {{validate_ap}}."
Answer: 116455.0

User story: "Digest and parse headers from fits files provided by the camera. These will be use to augment the templates that will produce telemetry to mock meta-data to be captured by the new header client."
Answer: 40293.0

User story: "Following [~<USER>'s instructions, process an HSC RC dataset on lsstvc using a latest weekly."
Answer: 25957.0

User story: "Select and integrate metrics and key performance indicators to prototype service monitoring. "
Answer: 86766.0

User story: "Integrate existing lower-level nagios information into service level monitoring prototype."
Answer: 216297.0

User story: "Service Catalog Dependency Mapping"
Answer: 86769.0

User story: "Develop ITSM process for Incident Response"
Answer: 46392.0

User story: "Develop ITSM process for Incident Response"
Answer: 46393.0

User story: "Incremental refinement of the Service Catalog."
Answer: 7.0

User story: "Complete MagicDraw training and convert service catalog from EA."
Answer: 8.0

User story: "Please create these links:     {code:java}  ln -s /datasets/refcats/htm /datasets/comCam/repo/ref_cats  ln -s /datasets/refcats/htm /datasets/decam/repo/ref_cats    ln -s /datasets/refcats/htm /datasets/hsc/repo/ref_cats  {code}    Currently this is the only way to use the HTM reference catalogs."
Answer: 1554.0

User story: "Occasionally, we observe lsstsw driven builds hanging for extreme periods of time (> 8 hours).  This could be prevented by implemented a per job build timeout."
Answer: 345806.0

User story: "w_2017_12 doesn't build reliably due to a race in starlink_ast (DM-9881).    Even though {{shared_stack.py}} is smart enough to skip over w_2017_12 and install _13 (and later) weeklies, it doesn't mark any later weeklies as current.    It should."
Answer: 30.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 sole remaining boost_thread dependency in Qserv seems to be some thread-local storage used by the mysql qserv module.  Since the baseline minimal compiler is gcc 4.8, we can use C++11 thread_local instead."
Answer: 4283.0

User story: "Server side Rotation and Flipping is slow and require server calls which can demand large chunks of memory.  It is also problematic in the book keeping required for mask overlays and WCS matching. Performance could be better for time series tools and finder chart.    The browser now has the technology (HTML5 Canvas) to do the operations on the client side instantly.    Research and begin to work on these client side operations.  Work on or identify how to tackle the following issues:    # Using canvas to do the rotation  # Using canvas to do the flipping  # Finding and install packages to help with the affine transforms  # Using canvas to render images tiles instead of laying out div's  # Identify any new transforms coordinate systems.  # work on adapting the drawing layers.  # adapting wcs match and target match   # Converting downloading jpeg calls    For any work that is just identified but not completed make the related tickets and link them back to this one.    This branch should be kept separately from dev until we can do extra testing. There should be a separate ticket just for testing (link it back here). "
Answer: 38541.0

User story: "Prototype use of Elastic Log Search."
Answer: 1027827.0

User story: "Research use of Graylog"
Answer: 185379.0

User story: "Create a dashboard for each authorization mapping, e.g., admins, storage, scientists, developers, management."
Answer: 100412.0

User story: "Define alert policies and authorization mappings for the visualization component."
Answer: 100416.0

User story: "Deploy selected visualization component, including installation scripting and security vetting."
Answer: 50113.0

User story: "Define and implement data retention and access policy."
Answer: 100415.0

User story: "Deploy data storage component, including installation and configuration."
Answer: 50063.0

User story: "Define additional metrics to collect based on initial user feedback"
Answer: 50206.0

User story: "Deploy selected metric collection agent on cluster. Configure cluster nodes to store and forward logs to monitor node."
Answer: 17.0

User story: "Look into existing tools and packages to provide system monitoring and display. "
Answer: 17.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: "Running this same test command on lsst-dev    {code:java}  processCcd.py /datasets/decam/repo/ --calib /datasets/decam/calib/cp201302/ --rerun private/<USER>w2017_13 --id  visit=177347 ccdnum=3 -C $OBS_DECAM_DIR/config/processCcdCpIsr.py --config  calibrate.doAstrometry=False calibrate.doPhotoCal=False isr.assembleCcd.setGain=False  {code}    works with stack w_2017_11 but fails with w_2017_13.  First error:    {code:java}  processCcd FATAL: Failed on dataId={u'date': '2013-02-12', 'visit': 177347, u'hdu': 36, 'ccdnum': 3, u'filter': 'u'}: Unable to retrieve cpBias for {u'date': '2013-02-12', 'visit': 177347, u'hdu': 36, 'ccdnum': 3, u'filter': 'u'}: Mapped path should not be absolute.  {code}  "
Answer: 9866.0

User story: "Executor creates a dataset repository from scratch by setting up directory structure recognized by Butler. The new Butler expectations with that regard differ from those in its previous version. As a consequence, Executor must be refactored to accommodate the changes."
Answer: 87550.0

User story: "The lsstdoc.cls file defines standard macros for referring to core documents but not all of these are found in the shared bibliography in lsst-texmf. Add these missing documents. Also redefine the {{\ds}} macro to use a citation rather than a direct docushare link."
Answer: 72.0

User story: "Test correctness, robustness and efficiency of the generic DAX generators using example workflows."
Answer: 89097.0

User story: Generic generator of Pegasus DAXs needs to be thoroughly tested. For that a reasonable sized sample of actual workflows is required. The idea is to "encode" a few existing workflows in some commonly used graph format (e.g. JSON, GraphML) and use them to evaluate robustness and efficiency of the DAX generator.
Answer: 66296.0

User story: "Two components of the current prototype of the batch production framework (Pegasus DAX generator and Executor) interact heavily with Butler which recently was a subject of a major refactoring.  The goal is to find out if and how changes introduced in Butler's API affect those components."
Answer: 14289.0

User story: "LDM-151 doesn't cite LSST documents so they don't appear in references. They need to be added."
Answer: 17458.0

User story: Having demonstrated (in DM-10044) that the QA plotting scripts work, make a plan for how we need to maintain and upgrade them. In particular:    - Make sure they follow the regular LSST coding conventions;  - Make sure they are committed to the master branch of some repository;  - Remove any HSC-specific code;  - Refactor/update/revise etc as necessary to make them suitably idiomatic.    (NB this ticket really is "make a plan" not "do all the above work" — I'd imagine you might spawn one or more tickets for the various upgrades needed).    In the process, consult with the SQuaRE group (probably [~<USER> is the first point of contact) to see how the scripts can be most conveniently made useful to the rest of the project — consider e.g. integration with SQuaSH or similar.
Answer: 98052.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: Take the scripts provided by [~<USER> and apply them to a reprocessing of the HSC RC dataset (either that generated by DM-10043 or some other recent job) to generate the "standard" series of QA plots.
Answer: 45888.0

User story: "Using instructions provided by [~<USER>, demonstrate that you can shepherd processing of an HSC RC dataset on Tiger or Perseus. Use a current LSST stack (e.g. the latest weekly at the time you start)."
Answer: 99204.0

User story: "meas_base's [{{CatalogCalculationConfig}}|https://github.com/lsst/meas_base/blob/0b6c81b6fe40f3d0e39237a9a83394b219cce41a/python/lsst/meas/base/catalogCalculation.py#L104] claims that it is:    {quote}  Default CatalogCalculationConfig. Currently this is an empty list, meaning that there are no default plugins run. The config object for each plugin must use this variable to specify the names of all plugins to be run  {quote}    This is wrong in a number of ways — it's not a list, it's not empty, and it doesn't make sense for each plugin to have to specify the names of all other plugins in use.    Please fix it."
Answer: 8665.0

User story: "Point in time (ie, daily) snapshots should being made of the canonical s3 bucket for published eups packages (eups.lsst.codes).  This could go to another s3 bucket or (perhaps better) into glacier."
Answer: 41760.0

User story: "The awscli subcommand {{aws s3 sync --delete ...}} removes files but not empty directories.  A simple additional step to remove empty directories needs to be added to the {{s3sync}} script/container."
Answer: 7194.0

User story: "Minimal containerized implementation of jupyterlab: no stack, indeed, no external modules, only one kernel.  Basically just what you need in order to run a Python notebook on top of our standard Centos image."
Answer: 9971.0

User story: "While working on DM-8854, the unit test for Rotate class, I noticed that it needs some minor refactoring.    After investigating how this class is used, I found that the class just needs some document.  I added the algorithm and   brief description what it is doing.      This ticket can be closed.  "
Answer: 7213.0

User story: "DM-9678 should be developed in the context of ongoing PSF work elsewhere. I need an awareness of what algorithms are currently developed, and (preferably) what new capabilities are being worked on in the near future.    This ticket should take as its starting point PSFEx (see RFC-312) and PIFF, but should expand to include other current software. Results should include advantages and disadvantages of each system, especially with respect to the requirements of image differencing, DCR correction, and other downstream image operations."
Answer: 108074.0

User story: "Improvement of forced photometry demo code.    * Incorporate code suggestions from [~<USER> made as part of DM-9420  * Transfer to a repository under the lsst organization, with a name like {{firefly_lsst_ex}} that will contain LSST-specific examples for Firefly"
Answer: 1018252.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: "Notify users, plan for process, and remove access to NFS disks."
Answer: 77774.0

User story: "Identify web services and related file that need to be moved due to GPFS migration, and begin transfer as needed."
Answer: 27196.0

User story: "Identify non-project-level data that needs to be moved to GPFS, and begin transfer as needed."
Answer: 27201.0

User story: "Determine network connectivity and hardware needed for the DAQ. Procur hardware as necessary."
Answer: 1.0

User story: "Produce a proof of concept filtering system given the research done in the previous issue."
Answer: 49022.0

User story: "Knowing that the internal intermediate persistence format for alerts is likely to be Kafka+Avro, research stream filtering technology that will fit into that ecosystem."
Answer: 20253.0

User story: "Our [unittest policy|https://developer.lsst.io/coding/unit_test_policy.html] does not describe how to balance tests between python and C++, for code that is mostly or entirely C++ (with pybind11 wrappers). After [this conversation on Slack|https://lsstc.slack.com/archives/C2JPL8U78/p1490810875329941], it was clear that the consensus is that tests of our C++ layer should be written almost entirely in python, with C++ tests only for purely internal C++ APIs or tricky things in the pybind11 layer (both of which should be rare).    Filing as a ticket instead of an RFC, given the clear consensus in the Slack conversation. I can make an RFC if someone does object."
Answer: 1841917.0

User story: There are timing debug statements that should either be removed or made less verbose after   a month or two of testing has been done on the PDAC. The lines of code affected are labeled with "TEMPORARY-timing".  
Answer: 1623306.0

User story: "Make final backup of NFS user partition(s)."
Answer: 14.0

User story: "Review procedures with NCSA Security to assure compliance with accepted practices."
Answer: 193229.0

User story: "Process refinement and improvement: automating backup processes. Processes are currently run with sysadmin involvement. Manual processes will be replaced with scripts, cron jobs, etc."
Answer: 213335.0

User story: "Inserting the task template we've made into the proper place for it."
Answer: 1851818.0

User story: "The state of a bokeh app is controlled by a set of url parameters, different apps may share the same parameters like the {{ci_id}} and {{ci_dataset}}. We propose an API endpoint to provide the default values for those parameters to the apps.    Right now the superset of parameters use to control the apps are:    {{ci_id}} - the latest ci job id, otherwise {{None}}.  {{ci_dataset}} - default to the first dataset registered e.g. {{'cfht'}}, otherwise {{None}}.  {{ci_metric}} - default to the first metric registered e.g. {{'AF1'}}, otherwise {{None}}.  {{snr_cut}} - default to 100    "
Answer: 8710.0

User story: "Ensure that the reducer subtask correctly sets the mask to invalid for pixels where the reduced exposure is infinite or NaN."
Answer: 113670.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 discussion at the 2017 JTM, [~<USER> will provide a requirements document for Jointcal before the end of May 2017."
Answer: 238925.0

User story: "When you pass an {{Exposure}} with a {{Filter}} or {{Detector}} set to {{_standardizeExposure}} they are overwritten.      The latter is merely annoying (you have to set it again), but the former causes an exception when the Filter was set from the metadata;  before {{_standardizeExposure}} sees the {{Exposure}} the keyword {{FILTER}} has been removed so it goes and looks at the {{dataId}} which may not include the filter name (e.g. {{obs_comCam}} data from {{TS-8}})."
Answer: 101900.0

User story: "A new implementation of robust coaddtion similar to SafeClippedAssembleCoadd. Main differences is that it will use Psf-Matched Warps and mask artifacts that appear in more than one warp."
Answer: 178586.0

User story: "Please provide a ~page of hints for setting appropriate parameters when generating PSF matched coadds.    Per discussion of 2017-03-29, we reckon this should go into Doxygen."
Answer: 83242.0

User story: There are several things that came up in talking through the current dataflow diagram in the draft branch of LDM-151, several updates were identified.  I'm assigning this to [~<USER>, but I'm happy to have him hand it off to me or someone else.  * Alert Generation box needs template as input  * Between Alert Generation and Alert Distribution, the box says DIAObject, but that's not strictly true since now postage stamps exist with each DIASource  * Alert distribution is shown as a tan box which implies that it is a pipeline, but in reality is that it is a completely separate system.  In fact, I image the system as function by having Alert Generation post the "alerts" directly to that system.  
Answer: 53164.0

User story: "Before starting work on DM-9678 in earnest, I need to familiarize myself with the existing framework. A quick look at the stack documentation suggests PSF code is scattered across multiple packages (e.g., {{afw::detection::Psf}}, {{meas::algorithms::ImagePsf}}, {{meas::algorithms::PsfCandidate}}, {{pipe.tasks.measurePsf}}), so untangling things may not be trivial."
Answer: 51792.0

User story: "Given a CModel fit from a command line processing task, we should be able to exactly reconstruct the data that went into the fit, so we can re-run CModel with different configurations and investigate the best fit model & residuals."
Answer: 148352.0

User story: Where "literature" likely means the relevant section of the HSC pipeline paper, provided by [~<USER>.
Answer: 273952.0

User story: "This work originates on [HSC-1337|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1337], but the implementation should be done on LSST. The original ticket reads:    {quote}  We want to add fake objects into the coadds, rather than tracking them all the way through visits and building the coadds. Check that the fake injection works on coadds.  {quote}"
Answer: 100845.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 its current implementation, the NMF deblender using proximal operators cannot apply both the monotonicity and symmetry constraints on the same object. This is unfortunate, as the monotonic operator works quite well except that it can include non-symmetric features that are not present in the data, and the symmetric operator also works great except that it can steal flux from neighboring sources because it is not monotonic. It's worth investigating the possibility of projecting the constraints onto a joint space that will 1) Be more likely to converge and 2) allow both symmetry and monotonicity constraints (and perhaps others?) to increase the effectiveness of the new deblender."
Answer: 41955.0

User story: "Per meeting of 2017-03-29, review the SpanSet & Footprint APIs before DM-8108 goes for review."
Answer: 41972.0

User story: "DM has no formal requirements on how well we will process crowded fields; this needs to be fixed.    This is clearly a DRP science responsibility, but the DRP Scientist has no experience in this domain, so help/advice would be very welcome (I know at least [~<USER>, [~<USER>, [~<USER>, and [~<USER> have more experience with this than I do).    Here's my rough plan for how to start:   - Find some examples of data at different galactic latitudes LSST, spanning the space of what LSST will observe (or the equivalent in stellar density due to other substructure).  Ideally this would be HSC, DECam, or CFHT data.   - See how well DM processing currently handles these datasets.   - See how well a specialized crowded-field code handles these datasets.    I'm hoping that will help to reveal the quantities we'll actually want to put requirements on.    I do not anticipate starting this work until May 1 at the earliest; the April sprint is already quite overbooked for me."
Answer: 73845.0

User story: [~<USER> has written a prototype data reduction pipeline for the Auxiliary Telescope. [~<USER> should become familiar with how it works, on both a practical ("press button X, Y happens") and theoretical level ("why is Y useful?") level.    This work is likely a close collaboration between Merlin & Augustin. We can most conveniently account for that by double-loading it with SPs (ie, when the two are collaborating, they burn 2 SPs every four hours of work).
Answer: 102379.0

User story: "Audience is the PST-SC Chairs telecon scheduled for April 18th.    Should be able to mostly reuse slides from last P&CW, with some updates from LDM-151."
Answer: 37780.0

User story: "Please transfer appropriate CTIO 0.9m datasets to NCSA in order to facilitate the construction and test of obs_ctio0m9."
Answer: 13578.0

User story: "Building on the work done by [~<USER> in DM-9363, provide an obs_ package that can be used with data from the 0.9m at CTIO."
Answer: 46634.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 generating images of untrimmed CCDs from files such as those from the LSST camera (with amplifier images in different HDUs) or phoSim (with amplifier images in different files) it is very convenient to be able to assemble the entire CCD with overscan and extended registers included;  in fact, this is the way that many CCD cameras write their data.  When we do this, we need to update the amplifier bounding boxes to reflect the new reality.    We also need to generate modified bounding boxes when the electronics is reconfigured without updating the camera geometry model (in particular, changing the number of overscan pixels);  this means that we need to be able to build {{Detector}} objects on the fly.    When this was discussed on slack [~<USER> proposed that instead of modifying the bounding boxes in the first use-case that we modified the methods that return the bounding boxes.  I think that this is not viable as  - in order to present a consistent API this would require modifying functions such as {{getRawBoundingBox()}} in such a way that they are not just getters (this is not a show-stopper, but contradicts the approach that says that the amplifiers are simple afwTables)  - this doesn't solve the second problem, where we reconfigure detectors dynamically."
Answer: 6324.0

User story: "I count 28 exposures available.  I should fit these and start looking through them to see, for example, how the rotator angle affects things, or how elevation angle affects things...    End product of this is a document that describes the results of this work to date. (Preferably as a DMTN).  "
Answer: 456425.0

User story: "Now that I can fit full focal planes of donuts, it would be nice to have some tools to assure the quality of those fits and investigate outliers.  Useful scripts would include:    Scatter plot of fit params as a function of field-of-view.  Plot individual donuts + models + residuals.  Plot indicating which donuts passed donut selection cuts.    I have hacky versions of all of these, but it would be nice to collect them all somewhere more official and ensure that they play nicely with the stack (that they use the butler, for example)."
Answer: 103441.0

User story: "In order to read LSST data with one amplifier per HDU and no {{INHERIT}} keyword (which isn't a FITS standard (yet?)) we need to be able to read the header as a part of a composite dataset.    Please add a formatter to read {{PropertyList}}s.  "
Answer: 2383.0

User story: "The size of a {{Wcs}} pickle increased in DM-7152 (due to [this commit|https://github.com/lsst/afw/commit/74b8006f9bdddcecbf78bb979895f776330b157f]). It needs to be reduced so as to maximise the number of inputs a coadd may have (since a list of {{Wcs}} is transmitted over the wire in the coaddDriver, and pickle in python 2 has a size that must fit in an {{int}}); we are hitting the limit when coadding Cosmos y-band data from HSC."
Answer: 450.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 metrics don't have diagnostic plots associated to them, either because they are not implemented yet or because they don't exist at all.      In either case we should disable the drill down from the monitor app or implement an empty app with a place holder for the diagnostic plot."
Answer: 970915.0

User story: "{{PsfexPsfDeterminerTask.determinePsf}} uses two undefined variables: {{pcval}} and {{pc}}    I suggest cleaning up all the python code so it passes pep8. That would make it much easier to spot serious errors such as this (since right now they are buried in a sea of minor violations).    Speaking of which: this could be a really nice time to fix DM-4905, as well -- another undefined variable spotted by flake8.  "
Answer: 1839388.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 Statistics class predates many of the classes that we now use with it, and its design has slowly become a pain point that we tend to work around rather than fix.  It's time for a redesign.    One centerpiece of that redesign should probably be DM-2415: use ndarray instead of the image classes as the primary data class {{Statistics}} interacts with.  That'd let us clean up a lot of helper classes (since it's easy to get an {{ndarray::Array}} from an {{Image}}, but hard to do the reverse in general).  I'd also like to see {{Statistics}} interoperate with the new {{SpanSet}} functor interface somehow, which would let us compute statistics on a set of pixels whether those pixels are in an {{Image}}, a 2-d array, or a flattened 1-d array from e.g. a {{HeavyFootprint}}.  And it'd be nice to address DM-3156 (support using a column from a Catalog even when that catalog is not contiguous) as well.    We should also update how Statistics is configured: since the {{Statistics}} was written, we've switched to a new configuration package (pex_config; yes, at one point it was new) that brings with it a new convention for configuring C++ objects.  We've also made it possible to use keywords arguments in Python interfaces, which may make some configuration interfaces palatable that were not before.    {{Statistics}} also plays an important role in coaddition, because we use it to compute the value of  each coadd pixel from the warped CCD-level pixels at the same position.  There are currently some problems with this captured in DM-4158 (provide more options for statistics to use in coaddition) and DM-9953 (we need more control over how we use the mask values of input pixels to set the mask values over output pixels).  So this redesign will also include redesigning (to perhaps a lesser degree) the {{afw::math::statisticsStack}} functions that do this work.    Beyond those requirements, we of course need to keep at least most of the functionality of the current design; if you see something you think is vestigial, please check before removing it.    I do not think we want to be constrained by the current interface in any way - as long as the same functionality is supported somehow, breaking backwards compatibility is acceptable (and expected).    This ticket is to more concretely gather requirements from features of the current codebase and the above feature requests, and to produce an initial design sketch to meet those features.  Implementation should be on one or more additional tickets.    [~<USER>, [~<USER>, [~<USER>: if you can think of any other tickets (or unticketed problems) that would put requirements on a Statistics design, please comment here."
Answer: 103613.0

User story: "The new and currently best HSC calibration data are available at http://tigress-web.princeton.edu/~pprice/CALIB-LSST-20170105/     A subset is already on the LSST cluster at {{/scratch/pprice/madcash/CALIB-LSST-20170105/}}."
Answer: 10140.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "The function {{plotSuite}} in {{tractor.py}} uses the variable {{y}} before defining it (at least it appears to)."
Answer: 1844622.0

User story: "LDM-151 is currently using a default Latex style. It needs to be ported to use the standard look and feel {{lsstdoc.cls}}."
Answer: 2752.0

User story: "During KPM tests we found that some interactive queries were being put into the scan scheduler rather than the group scheduler:    {code}   QuerySession description:    original: SELECT o.deepSourceId,o.ra,o.decl,s.coord_ra,s.coord_decl,s.parent FROM Object o,Source s WHERE qserv_areaspec_box(306.208311,-22.615502,306.237230,-22.530038) and o.deepSourceId=s.objectId    has chunks: 1    chunks: []    needs merge: 0    1st parallel statement: SELECT o.deepSourceId,o.ra,o.decl,s.coord_ra,s.coord_decl,s.parent FROM LSST20.Object_%CC% AS o,LSST20.Source_%CC% AS s WHERE scisql_s2PtInBox(o.ra,o.decl,306.208311,-22.615502,306.237230,-22.530038)=1 AND scisql_s2PtInBox(s.coord_ra,s.coord_decl,306.208311,-22.615502,306.237230,-22.530038)=1 AND o.deepSourceId=s.objectId    merge statement: SELECT o.deepSourceId,o.ra,o.decl,s.coord_ra,s.coord_decl,s.parent    scanRating:15  ScanTable: LSST20.Object lock=1 rating=5    ScanTable: LSST20.Source lock=1 rating=15  {code}    The {{scanRating}} setting should be zero for such a query."
Answer: 32864.0

User story: "in this block:  {quote}  2.16.9   Composite Policy  To indicate that a dataset should be serialized/deserialized from components, the policy’s dataset definition has a keyword composite. The structure is:  {code}  <dataset type name>: {      composite: {          <component name>: {              datasetType: <dataset type>              setter: <method name of setter>              getter: <method name of getter>              assembler: <importable function to do custom deserialization>              disassembler: <importable function to do custom serialization>              subset: bool              inputOnly: bool          }          ...      }  {code}  {quote}  assembler & disassembler are in the wrong spot, the need to be below ‘composite’ not ‘componentName’"
Answer: 105081.0

User story: "See mail from Wil O'Mullane, 2017-03-25."
Answer: 1120.0

User story: "The profiler we recommend using in the developer guide isn't provided as part of the stack, and isn't entirely trivial to build on most operating systems (though it's not hard).    This ticket will provide eupspkg builds for igprof and its dependencies.  Hopefully that will make it easy to also make it eups-distrib-installable in the near future, though it shouldn't ever be a dependency of any stack packages (or metapackages).  "
Answer: 92086.0

User story: "ctrl_pool's {{--time}} is easily confused with the inherited {{-t}} from CmdLineTask, which makes it easy to use the wrong one and get your batch jobs killed too early.  We should always be forced to provide a time estimate when submitting to a real batch system."
Answer: 150.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 appears to be a bug in the monotonicity operator that causes some edge pixels to wrap monotonicity around the edge to the next (or previous) line. The cause of this needs to be found and fixed."
Answer: 63.0

User story: When the search result in IRSA catalog search is empty, the IRSA catalog search shows the table with empty row data.  The LSSTCatalogSearch returns the message with "no data found".   I think that the behaviors in two catalog searches should be consistent.       Since the meta server is not available, the data definitions are obtained from the search result.  When there no data is available, there is no data type definition either.  The current implementation threw an exception when the empty table is returned from the PDA search.  But for multi-object search, the exception will stop further searches for the other object.  For now,  it is modified as below:  # Let getDataFromUR return null if the result is empty  #  When the PDA search returns empty, the exception in LSSTCatalogSearch is deferred at the loadFile  # In LSSTMutliObjectSearch, when one of the callable returns empty result, it will be skipped. Thus, all targets in the input file will be searched.    NOTE:  When the meta server is working, the above implementation will be changed accordingly.   So is the meta definition in LSSTQuery.             
Answer: 23214.0

User story: "I'd really love to kill these log messages, which we've all gotten used to (but are always confusing to new users):    {code}  CameraMapper INFO: Unable to locate registry registry in root: registry.sqlite3  CameraMapper INFO: Unable to locate registry registry in current dir: ./registry.sqlite3  CameraMapper INFO: Unable to locate calibRegistry registry in root: calibRegistry.sqlite3  CameraMapper INFO: Unable to locate calibRegistry registry in current dir: ./calibRegistry.sqlite3  {code}    My understanding is that no one finds these useful."
Answer: 1708585.0

User story: "Deblending results in the form of HeavyFootprints should be available to users, which means they must be stored.    This proposal should include an estimate of how much storage this will require for a given area of sky, which can probably be derived from the average HeavyFootprint size in HSC data.  This will be a function of depth, so it will not be the same at the beginning of the survey as it will be at the end (but we should have HSC data that spans those depths).    This will be a conservative estimate - it is possible that deblender outputs may take a form that allows them to be highly compressed and quickly reconstituted given coadd data.    We will not consider the possibility that it will be necessary to store per-epoch HeavyFootprints for ForcedSources."
Answer: 11358.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 a package for {{treecorr}}  to allow for calculation of correlation functions in a fast, robust, and tested code.    This will not add dependencies to {{lsst_apps}} or {{lsst_distrib}}.     Implementation is likely  1. Create wrapper install packages for {{treecorr}}.  2. Figure out how to avoid adding the FITS reader dependency in {{treecorr}}.  3. Add treecorr dependence to {{validate_drp}} table file.    TreeCorr is a  "[c]ode for efficiently computing 2-point and 3-point correlation functions" and is being proposed for use in {{validate_drp}} to calculate the correlation function of the PSF residual ellipticity (DM-8951).  The GitHub repo is here:    https://github.com/rmjarvis/TreeCorr    TreeCorr depends on the following Python packages.    numpy  future  fitsio  pandas  pyyaml  cffi  
Answer: 177010.0

User story: "[ ] Create wrapper install packages for {{libffi}} and {{cffi}}    This is in support of installing the {{treecorr}} cross-correlation package and implementing RFC-296.    This might be easy as libffi is installed on most systems.  But this might make it a bit more difficult to test and make sure this has been done right.    One system it's not on is CentOS 7.3, which is what {{lsst-dev}} runs.        probably easy but not something I know how to do just off the top of my head; it's also something is likely already instlled on most systems, so we should decide whether to detect the already-installed system version."
Answer: 175913.0

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

User story: "Bucket ticket to cover non-specific SuperTask collaboration activities (see linked meeting notes)."
Answer: 1.0

User story: "Test variations of:    - L1, L0 sparsity  - Symmetry  - Monotonicity   - Exact (fractional) positions  - Combinations of the above    For runtime and results in the framework of DM-9172 and DM-9784.    The goal at the end of this ticket is to have a framework built up to display comparisons of the current deblender, the new NMF deblender, and simulated results (when applicable) so that we can identify successes and failure points of the new deblender.  "
Answer: 136919.0

User story: "This will be another test in the test notebook showing how well the overlap in the simulations matches the overlap in the analysed data."
Answer: 23.0

User story: "RFC-303 approved the principle that we can mandate a CentOS7 baseline operating system that requires a devtoolset to build the stack. This ticket is to demonstrate that a stack can build and run using devtoolset-6 on CentOS7 without running in to problems. A successful outcome should result in an RFC requesting a new compiler baseline."
Answer: 235091.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Currently the PSF convolution operator is a collection of 2D sparse arrays, which are different for each band, that converted are into full arrays in order to use [~<USER>'s proximal operator algorithm. Since the current simulated data is PSF matched, the processing time can be significantly reduced (by several orders of magnitude) by using the PSF operator as a sparse matrix in each band.    This fix is temporary so that we can profile and test PSF convolution and other features of the new deblender but  it is expected that this section of the code will be re-written in C++ in the final deblender before it is merged into the stack in a future sprint."
Answer: 16534.0

User story: See RFC-304.    I'll do something to support the desire to keep -1 to mean "the last HDU", although I do not plan to support this now (a fits file doesn't declare how many HDUs it contains, so we'd have to count them).  In C++ using the most negative int makes sense as the default value, and I assume that pybind11 can keep that as a default value.    
Answer: 13740.0

User story: "make sure the current catalog search processor handles WISE catalog data search properly"
Answer: 89287.0

User story: "Add capabilities to search WISE dataset, catalog and images    For catalog search, make it the same as current IRSA catalog search, assuming we have the MetaServ from SLAC ready. We need to use the result from MetaServ to layout catalog search panels so we don't need to make any changes when new catalog tables are added as long as the tables are returned by the MetaServ.     Do the same for image search.    This ticket also absorbed the work in DM-10284.  "
Answer: 89289.0

User story: "Learn enough about plotly to create multi plot component.  It should do the following:    - not be aware of tables  - put up the correct tool bar based on the plot type  - be aware of the traces that are in the plot  - know how to handle handle each trace type  - have an option in the toolbar that allows the user to switch between the traces to operate on  - have a way for the tool bar to be extended when a wrapper is connecting the plot to a table  - Do something similar with the side bar options."
Answer: 84954.0

User story: "Use plotly to create a version of the scatter charts.  Use the plotly heat map to create a version of the density plots"
Answer: 37132.0

User story: "Learn plotly and make a plotly version of the histogram chart"
Answer: 24187.0

User story: "Setup plotly environment:    * Set up how we are going the load plotly using a deferred load  * Create a plotly react wrapper  * set up Firefly environment to  contain a property to switch between plotting packages"
Answer: 6851.0

User story: "Current form of LSST latex class does not correctly declare whether a document is under change control. Add this facility."
Answer: 4252.0