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: "Verification dataset meetings, Illinois DES meeting, single-frame processing discussions, supertask meeting, OpenStack User meeting"
Answer: 7186.0

User story: "Document our procedures for collaborative development with JIRA, Git and GitHub for the new docs."
Answer: 38979.0

User story: Changes to deblender to propagate the "merge.peak" flag for parent objects as well as children. Relevant commit is 8aa3e8afdea938d5ff93292bc183bc5f39060842 from meas_deblender
Answer: 73426.0

User story: "In hsc the default behavior for the detection task is to updated footprints with a footprint which has been grown by the psf. This behavior needs to be ported to LSST, as some source records have footprints which are too small. When making this change, the new default needs to be overridden for the calibrateTask, as it needs the original size.    The port includes 8e9fb159a3227f848e0db1ecacf7819599f1c03b from meas_algorithms and 8bf0f4a44c924259d9eefbd109aadec7d839e0f2 from pipe_tasks"
Answer: 83390.0

User story: "DM-3692 cherry-picked the HSC ticket HSC-966 which allows for a set fraction of stars to be reserved from PSF fitting. Write a unit test to check that this functionality works correctly."
Answer: 1906940.0

User story: "I'm using Splines and LevenbergMarquardt stuff from the Eigen 'unsupported' modules. Is it possible to include the unsupported modules in the LSST stack?"
Answer: 297274.0

User story: "In ctrl_pool's pool.py, we have a Comm class that appears to work around an OpenMPI bug.  In his review for DM-2983, [~<USER> requests that we check whether this is still necessary."
Answer: 2237982.0

User story: "Evaluate the use of light-weight SQL, such as InnoDB, TokuDB (now Kyoto Cabinet), or RocksDB to create and manage the secondary index."
Answer: 96654.0

User story: "The exampleCmdLine task worked fine, need to show demo for other tasks from pipe_tasks"
Answer: 354391.0

User story: "The test/testDagIdInfo.py because it runs a script from bin.src, rather than bin.   This test needs to be rewritten."
Answer: 289.0

User story: "The default timeout value for aborting a multiprocessing run in CommandLineTask is too short. Currently if no time length is supplied by the user, the default value gets set to 9999s. However if a processing task is quite large it is possible for the processing pool to take much longer to arrive at the result. Currently if the processing pool does not complete it's run within that time limit, python multiprocessing will throw a timeout error. The timeout value should be scaled such that the supplied value is assumed to be the timeout length for one processing task, and should be scaled by the number of tasks divided by the number of cpus available. The command line task documentation should be updated to reflect this change."
Answer: 2242403.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's a test in ctrl_execute that exercises the bin/dagIdInfo.py test program.   Since the rewrite_shebang rewrites happen after the tests are executed, the test that looks for the bin/dagIdInfo.py binary fails, since it's not there before the tests execute."
Answer: 73.0

User story: "A particular cmsd configuration parameter prefixes a hardcoded path for QueryResource, which needs to be removed. This seems to appear only during multi-node tests."
Answer: 4311.0

User story: "A script for performing pipeline output QA is under development for HSC.  The script provides many useful tools for plotting and analyzing pipeline outputs on single visits and coadds.  This is of general use for LSST and, in particular, will be adapted/expanded to include tools for the direct comparisons of identical data sets processed with both the HSC and LSST pipelines (i.e. DM-2984).  Appropriate adaptations for this script to run with the LSST stack will be made here (with the understanding that development is still ongoing on HSC and further adaptations will be accommodated as necessary/desired).    See [HSC-1320|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1320] and [HSC-1359|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1359] for details and examples of the output of this script."
Answer: 47500.0

User story: "Qserv saves logs from failed unit tests in a non-standard location and they are not currently visible in jenkins. It would be nice to include those logs (if they exist) in jenkins output. The logs are in multiple directories inside {{build/}}, the pattern to search for the logs is {{build/\*/\*.utest.failed}}.  "
Answer: 1034192.0

User story: "The {{git-lfs}} client is deprecating some features that we are using with v2.0.    They are deprecating {{.gitconfig}} in favor of {{.lfsconfig}}. They are also removing the {{git-lfs init}} command. We will need to update documentation, all repos that use git-lfs and CI system.    See: https://github.com/github/git-lfs/issues/839"
Answer: 651117.0

User story: "ProcessCcdDecam needs some cleanup:  * {{run}} method simply delegates to the base class  * {{propagateCalibFlags}} is a no-op (deliberately in {{cab69086}}, need to explore if the original problem still exists)  * The config overrides (in config/processCcdDecam.py):  ** Uses the catalog star selector, which isn't wise given the current heterogeneity of reference catalogs.  ** Sets the background {{undersampleStype}} to {{REDUCE_INTERP_ORDER}}, which is the default."
Answer: 239.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 czar caches empty chunk list after it reads the list from file. This complicates things when we need to update the list, integration test for example has to restart czar process after it loads new data to make sure that czar updates its cached list. Would be nice to have simpler mechanism to resetting cached list in czar without restarting it completely. It could be done via special query (abusing FLUSH for example) or via sending signal (problematic if czar runs remotely).    This can be potentially useful even after we replace empty chunk list file with some other mechanism as I expect that cache will stay around even for that."
Answer: 42927.0

User story: "* fix weird index sublist expansion bug  * with the current template, it's difficult to tell the difference between ===,---,^^^, sections  * add a .gitignore template  * add some sort of .travis.yml template  * possibly have travis push the master branch to readthedocs?  "
Answer: 2036638.0

User story: "Following the good principals of re-using prior work, review VAO/IVOA protocols for use in LSST IAM, in particular the [IVOA Credential Delegation Protocol|http://www.ivoa.net/documents/latest/CredentialDelegation.html] and include a summary in our LSST IAM Design Doc."
Answer: 380209.0

User story: "Personally establish Nebula as a stack development platform."
Answer: 1.0

User story: "Before this ticket, the files in {{testdata_decam}} are as they are downloaded from the archive.  Some are MEF, and the total is a bit big (1.2G).    I made a trimmed down version of {{testdata_decam}}, 109M and available here:  [https://github.com/<USER>testdata_decam.git]  I trimmed it down by only saving the primary HDU and one data HDU.  However the unit tests in {{getRaw.py}} become less meaningful and I am not sure if we really want to do this, because some complexities of DECam files are about the MEF. {{getRaw.py}} tests Butler retrieval of multiple dataset types, in particular tests if the correct HDU is retrieved.     Nonetheless, {{getRaw.py}} can pass  (with branch u/hfc/DM-4375 of obs_decam)    Note: the old testdata_decam still live on lsst-dev:/lsst8/testdata_decam/"
Answer: 1095.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: This is a port of [HSC-715: Add tract conveniences|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-715].  Here is the original description:    {panel}  In regular HSC survey processing, we'll run with a "rings" skymap to cover the entire survey area. meas_mosaic does not currently efficiently or conveniently iterate over tracts. For example:  {code}  mosaic.py /tigress/HSC/HSC --rerun price/cosmos --id field=SSP_UDEEP_COSMOS filter=HSC-R  {code}  Note the lack of a tract in the --id specifier — we want to iterate over all tracts. This is not currently possible. Instead, if we do not know the tract of interest (which the user should not be required to know), we have to iterate over all the tracts (e.g., tract=0..12345), but the user should not be required to know the number of tracts, and this is slow (and possibly memory-hungry: currently consuming 11GB on tiger3 just for 12 exposures).  We need an efficient mechanism to iterate over all tracts by not specifying any tract on the command-line.  {panel}    As this functionality was added specifically for {{meas_mosaic}}, it was going to be ported as part of DM-2674.  Due to a recent desire to use this functionality, this ticket will be ported here.
Answer: 24784.0

User story: "These repos were too large to move as part of the initial gitolite -> github migration.  They now need to be migrated to git-lfs.    https://dev.lsstcorp.org/cgit/LSST/DMS/    LSST/DMS/testdata/isrdata.git  LSST/DMS/testdata/multifit.git  LSST/DMS/testdata/sst.git  LSST/DMS/testdata/testdata_cfht.git    This spreadsheet: http://ls.st/md3 needs to be updated after the migration and the new canonical URLs should be announced on community since currently none of these repos are referenced from {{repos.yaml}}."
Answer: 38895.0

User story: "There is a package full with test data for the obs_decam.  It is an eups package currently, but not a git repository.  I would like to migrate that into our hosted git-lfs so the obs_decam package can be built by Jenkins.  [~<USER> I'm hoping you would be willing to handle this for me.  If not I can find somebody else.  Thanks!"
Answer: 31586.0

User story: The github lfs backed repo https://github.com/lsst/ci_hsc needs to be migrated to git-lfs.lsst.codes.  A sanity check for any other "live" lfs repos under the lsst github org might also be a good idea.
Answer: 92164.0

User story: "This is just a report of the amount of time it takes to run ShapeletPsfApprox and CModel over 10000 galaxies from GalSim"
Answer: 105462.0

User story: "We discovered during this Sprint that this plugin was giving us faulty values for all the models except for SingleGaussian.  I will fix that bug on this issue.    Obviously, a better unit test would have caught this.  I am adding a DoubleGaussian unit test, plus a test that the default models provide different results.  Also a timing test for all the models, as we do not really have enough information about the performance of the shapelet approximation.  "
Answer: 93694.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 default overscan correction from IsrTask is used for processing DECam raw data. Overscan subtraction is done one amplifier at a time.     However, a bias jump occurs due to the simultaneous readout of the smaller ancillary CCDs on DECam, some images show discontinuity in the y direction across one amplifier, as in the example screen shot.     This ticket is to improve overscan correction for DECam data so to mitigate this discontinuity in the ISR processing.    Arrangement of CCDs on DECam: http://www.ctio.noao.edu/noao/sites/default/files/DECam/DECamPixelOrientation.png      h3. More details:  There are 6 backplanes in the readout system, shown by the colors in DECamPixelOrientation.png. In raw data files, the CCD's backplane is noted in the header keyword "FPA".  Examination of some images suggests that science CCDs on orange and yellow backplanes show bias jump at 2098 pixels from the y readout. That is the y size of the focus CCDs.     h3. Actions:  For CCDs on the affected backplanes, divide the array into two pieces at the jump location, and do overscan correction on the upper and lower pieces separately.    
Answer: 3277.0

User story: "First stage demo of Super Task and WorkFlowTask Framework"
Answer: 9761.0

User story: "Need to add configuration to the CmdLineActivator in new Workflow tasks"
Answer: 9763.0

User story: "This story represents the implementation of the first part of the SuperTask framework design,"
Answer: 2.0

User story: Installing {{lsst_apps -t w_2015_45}} fails with    {code}  ERROR: ImportError: cannot import name six [unknown]  Traceback (most recent call last):    File "tests/getId.py", line 29, in <module>      from lsst.obs.sdss import SdssMapper    File "/Users/lsst/products/EupsBuildDir/DarwinX86/obs_sdss-11.0-3-g1664b15+1/obs_sdss-11.0-3-g1664b15+1/python/lsst/obs/sdss/__init__.py", line 24, in <module>      import makeCamera    File "/Users/lsst/products/EupsBuildDir/DarwinX86/obs_sdss-11.0-3-g1664b15+1/obs_sdss-11.0-3-g1664b15+1/python/lsst/obs/sdss/makeCamera.py", line 30, in <module>      from lsst.obs.sdss.convertOpECalib import SdssCameraState    File "/Users/lsst/products/EupsBuildDir/DarwinX86/obs_sdss-11.0-3-g1664b15+1/obs_sdss-11.0-3-g1664b15+1/python/lsst/obs/sdss/convertOpECalib.py", line 4, in <module>      from lsst.obs.sdss.yanny import yanny as Yanny    File "/Users/lsst/products/EupsBuildDir/DarwinX86/obs_sdss-11.0-3-g1664b15+1/obs_sdss-11.0-3-g1664b15+1/python/lsst/obs/sdss/yanny.py", line 35, in <module>      from astropy.extern import six  ImportError: cannot import name six  {code}
Answer: 1564.0

User story: "Write a technote about the platform that github.com/lsst-sqre/lsst-technote-bootstrap lets DM members publish in. Discuss current status and outline future plans."
Answer: 14921.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: With all recent development in CSS sector we should be able now to get rid of Python in czar entirely. This is also a good opportunity to move from XML-RPC between proxy and czar with direct in-process "communication". Daniel said it's a good idea :)  
Answer: 34980.0

User story: "{{2015_10.0}} has a build error under a current {{lsstsw/bin/deploy}} environment.  Current speculation is that this is related to the conda version of numpy being upgraded to {{1.10.1}}."
Answer: 105452.0

User story: "It's difficult to disentangle interleaved log messages when running with multiprocessing.  Two possible ways to do this would be:  1. Have each process write to a different log file.  Maybe we could allow the user to specify log filenames including {{%(pid)s}} and {{%(hostname)s}}.  More useful would be to allow the full range of keys from a {{dataId}}, but that might require some changes in how processing runs.  2. Prepend each line of the log with context information ({{dataId}}, pid, hostname), allowing the user to use {{grep}} to do the disentangling.  To avoid overwhelming the log with the context information, a hash of the context information could be used instead, with the lookups published in the log before the processing starts.        h5. Brief summary on the changes:  - Chain logs of sub-tasks to their parent task logs  - Add {{PrependedFormatter}} as the new default formatter for log files (specified through {{--logdest}} command line argument for {{cmdLineTask}}). The standard output to the terminal remains the same as before.  - Any string can be used to label a pex_logging Log, and with {{PrependedFormatter}} this label prepends each log message. For {{cmdLineTask}}, the dataId is prepended.  - The HSC's commit on prepending the timestamps is also ported to {{PrependedFormatter}}.  - An example log message:  {code:java}  2016-03-08T22:29:56.889933: [{'filter': 'r', 'tract': 0, 'patch': '2,3'}]: mergeCoaddDetections: Culled 1731 of 7751 peaks  {code}  "
Answer: 168520.0

User story: "Prompted by a email request from John Gizis."
Answer: 22.0

User story: "* Improve API with LDM-144: need to separate spec of czar nodes from spec of worker nodes  * Revisit model for qserv czar nodes  * Fix chunk count for DiaObject (dbL2 F139)  * Change low volume query result size, 0.5 GB --> 1 MB (sciReq G271).  * Revisit model for shared scans and multiple releases  * Add model for recovery from node failure for Query Access cluster  * Consider modeling intermediate results (concluded that intermediate results are relatively small, and given they are distributed across the cluster, it is not worth modelling them)  * Fix issue with transfer time of nightly products from Archive to Base  ---  * Add Dia* to scans  * Consider modeling nodes for data loading  * LDM-139 and LDM-141 don't document where MOPS Scratch comes from or what it's supposed to hold.  * revisit bulk data transfer from HQ to Base (shipping disks --> over the network)"
Answer: 1621490.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: "Version 5.8.0 of the ActiveMQ broker, which is not part of the regular distribution, is quite out of date.  [~<USER> is working upgrading the ActiveMQCPP library in DM-4330 to the current version, and this would be a good time to upgrade the broker to the latest release so we try and stay in sync."
Answer: 1321.0

User story: "(aggregation ticket for [previous existing]] tightly related tasks in progress related to binary distribution)"
Answer: 157460.0

User story: "Create a template repository for LSST (DM/SQuaRE) technical reports that are written in reStructuredText, built with Sphinx and published with RTD"
Answer: 2395.0

User story: "{{fitsthumb}} is now obsolete; all the functionality we need is available in {{afw}}. Further, we want to drop it as a dependency to make the job of integrating {{obs_subaru}} with CI easier."
Answer: 2818.0

User story: "Get SSL certificate and configure httpd for mod_auth_krb5 authentication in IAM test VM. Document the setup."
Answer: 39140.0

User story: "Configure [sssd|https://fedorahosted.org/sssd/] with NCSA LDAP for accounts in test IAM VM using instructions from Doug Fein."
Answer: 39028.0

User story: "Install MariaDB in our test IAM VM at NCSA and configure it for Kerberos password authentication. I understand that Kerberos ticket authentication is not yet supported by MariaDB. Document the process and include references to the ongoing work to add Kerberos ticket support.    Create example tables that demonstrate access control for different logged in users."
Answer: 49133.0

User story: "Install the DAX server (https://github.com/lsst?query=dax) in our test IAM VM at NCSA and configure it to use Kerberos authentication using standard Python flask Kerberos support. Document the process."
Answer: 218891.0

User story: "Configure sshd in our test IAM VM to use pam_krb5 so the user gets a Kerberos ticket when logging in as discussed in our design doc. Document the configuration steps."
Answer: 49121.0

User story: "Attend UIUC weekly meeting and give support as needed. "
Answer: 37453.0

User story: "Attend UIUC weekly meeting and give support as needed. "
Answer: 1.0

User story: "Follow instructions on:    https://confluence.lsstcorp.org/display/LDMDG/NCSA+Nebula+OpenStack+User+Guide  https://community.lsst.org/t/creating-a-nebula-instance-a-recipe/353    and create a nebula instance with the stack, update and install more packages in the stack, test by constructing a data repository and processing ISR with DECam raw images.    "
Answer: 20073.0

User story: "In DM-3663 we (= [~price]) provided an integration test for processing HSC data through the stack with the intention that it should be integrated with the CI system.    Having this test available and regularly run would be enormously helpful with the HSC port -- we've already run into problems which it could have helped us avoid (DM-4305)."
Answer: 170728.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: "Add a test task to Firefly's common build script.  This can be used by any sub-project to run unit test.  Added unit testing to Jenkins continuous integration job to ensure new code does not break unit testing."
Answer: 4029.0

User story: "Pandas was added to the bin/deploy script in lsstsw to support  sims development.  This has already been merged to master in 4b1d1a0fa.  The ticket is to ask that lsstsw be redeployed so the sims team can build branches that use pandas."
Answer: 105129.0

User story: "obs_lsstSim has seen some bitrot.  In particular, the ingest task and the addition of the getExposureId methods on processImageTask have not been propagated to obs_lsstSim.  This ticket will deal with those issues."
Answer: 234711.0

User story: "Add flux data model to capture menu and banner information.  Convert banner and menu UI from gwt to react.  As part of this task, bring in Fetch API to simplify client/server interactions."
Answer: 4349.0

User story: "We write up some introductory guides for Nebula usage to enable new users to get started.  These are located on Confluence under :    https://confluence.lsstcorp.org/display/LDMDG/NCSA+Nebula+OpenStack+User+Guide"
Answer: 142650.0

User story: "Boot openstack machines using vagrant, then deploys docker images and finally launch multinodes tests.    FYI, lack of DNS on OpenStack Cloud cause problems, but a vagrant plugin seems to solve this."
Answer: 114718.0

User story: "Spent 3 days in focused planning to knock out version 1 of the L1 system plan.  SPs cover me, Don."
Answer: 36641.0

User story: "IAM group attended DM bootcamp"
Answer: 86939.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending October 24, 2015."
Answer: 1.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending October 17, 2015."
Answer: 1.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending October 10, 2015."
Answer: 1.0

User story: "Support for lsst-dev cluster, OpenStack, and accounts  for week ending October 3, 2015."
Answer: 1.0

User story: "Either by wrapping, or by converting, make an existing task usable as a SuperTask subclass so that it can be run under an Activator."
Answer: 1608546.0

User story: "The fringe subtraction is not necessarily performed if {{doFringe}} is True. It is only if the filter of the raw exposure is listed in config fringe.filters.      Fringe data should not be read unless the filter is indicated. There are likely no such filter data and it would cause runtime errors.      Seems related to changes from RFC-26 and DM-1299. "
Answer: 15609.0

User story: "Create a design document covering the initial SuperTask concept and a scheme for how it would lead to solutions to longer-term pipeline construction problems, support provenance recording, etc."
Answer: 192671.0

User story: "Hold a teleconference design discussion with members of the SQuaRE team.  "
Answer: 109620.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: "Hold an in-person design discussion with members of the SQuaRE team.  "
Answer: 48.0

User story: "The API tokens issued by keystone expire after ~ 1 hour.  This is problematic for some automation tools, such as a packer, that do not expect to have to reauthorize after such a short period of time.  Between the short token TTL and DM-4237, there are significant difficulties in trying to make automated images avaiable.    {code}  ==> openstack-centos-7: Error terminating server, may still be around: Expected HTTP response code [202 204] when accessing [DELETE http://nebula.ncsa.illinois.edu:8774/v2/8c1ba1e0b84d486fbe7a665c30030113/servers/aacabacd-e0bc-4a4b-9892-0f2e474727c5], but got 401 instead  ==> openstack-centos-7: Authentication required  {code}"
Answer: 8307.0

User story: "This will create a test (not necessarily a unit test) that will simulate dipoles and measure them so that the measurement can be compared to truth values.  This may be simply refactoring the current tests.    This task should also include generating more generalizable utilities needed to create the dipoles and incorporating these and other test data into the stack so that they can be used in other studies."
Answer: 110953.0

User story: "There are tests in ip_diffim/tests/dipole.py for the dipole fitting.  There is also an example in the examples directory of ip_diffim.  This story will investigate these tests and examples to see to what precision the tests go as well as how complete the tests are.    An outcome of this will be an understanding of how precise the tests need to be to show that dipole measurement is behaving as we expect."
Answer: 110965.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: "Observed once [so far] building v11_0 with distrib install on centos 7 on a nebula m1.xlarge.  Packer destroyed the VM upon error so no triage could be done.    {code}    openstack:      openstack:      openstack: ***** error: from /home/vagrant/stack/EupsBuildDir/Linux64/meas_algorithms-11.0+1/build.log:      openstack: running tests/measure.py... running tests/testDetection.py... running tests/cr.py... running tests/CoaddPsf.py... running tests/testPsfAttributes.py... running tests/testCoaddBoundedField.py... running tests/testPsfDetermination.py... running tests/CoaddApCorrMap.py... failed      openstack: running tests/testLoadReferenceObjects.py... passed      openstack: passed      openstack: passed      openstack: passed      openstack: passed      openstack: running tests/testDoubleGaussianPsf.py... running tests/ticket2986.py... running tests/psfIO.py... running tests/psfSelectTest.py... running tests/Interp.py... passed      openstack: running tests/testGaussianPsfFactory.py... passed      openstack: passed      openstack: passed      openstack: running tests/testPsfCandidate.py... passed      openstack: passed      openstack: passed      openstack: passed      openstack: passed      openstack: passed      openstack: 1 tests failed      openstack: scons: *** [checkTestStatus] Error 1      openstack: scons: building terminated because of errors.      openstack: + exit -4      openstack: eups distrib: Failed to build meas_algorithms-11.0+1.eupspkg: Command:      openstack: source /home/vagrant/stack/eups/bin/setups.sh; export EUPS_PATH=/home/vagrant/stack; (/home/vagrant/stack/EupsBuildDir/Linux64/meas_algorithms-11.0+1/build.sh) >> /home/vagrant/stack/EupsBuildDir/Linux64/meas_algorithms-11.0+1/build.log 2>&1 4>/home/vagrant/stack/EupsBuildDir/Linux64/meas_algorithms-11.0+1/build.msg      openstack: exited with code 252      openstack: [ 43/53 ]  meas_algorithms 11.0+1 ...  {code}"
Answer: 27248.0

User story: "Support the distribution of a technical note SQR-001    - Remove oxford comma in author list (documenteer)  - Solve issue where title is repeated if the title is included in the restructured text document  - Solve issue where name of the HTML document is README.html"
Answer: 162.0

User story: "There are two stories in DM-3579 that define two requirements for the redesigned CalibrateTask.  Those along with the requirement that CalibrateTask be less brittle are a starting point for what the new task needs to do.  All other requirements should be gathered using the RFC process.    Using the input from the RFC and other requirements, the scope for this particular redesign will be defined and stated in a discourse thread."
Answer: 61939.0

User story: "We would a very simple way to make small reference catalogs for astrometry and photometry. The use case is testing and small projects, where the overhead of making a full up a.net index file (or whatever we replace that with) is excessive."
Answer: 132789.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: "Go through the literature to find relevant seminal papers on DCR.    The outcome will be a bibliography and executive summary.  This should be posted on Discourse."
Answer: 41738.0

User story: "{{obs_subaru}} should be included in the CI system."
Answer: 131080.0

User story: "Update data access docs, primarily LDM-135 and LDM-153. The work includes integrating the docs with data access epics."
Answer: 24507.0

User story: "Bi-weekly meetings with PO to discuss cyber security issues in LSST."
Answer: 38743.0

User story: "Local cyber security meeting at NCSA with DM group."
Answer: 38744.0

User story: When reloading the same 500MB RAFT image into an image viewer (see the script below), it was discovered that single node Firefy server with 3G memory runs out of memory after ~15 reloads    Test case: keep reloading the html file with the following Javascript, creating an image viewer with 500MB image:    function onFireflyLoaded() {          var iv2= firefly.makeImageViewer("plot");          iv2.plot({               "Title"      :"Example FITS Image'",               "ColorTable" :"16",               "RangeValues":firefly.serializeRangeValues("Sigma",-2,8,"Linear"),               "URL"        :"http://localhost/demo/E000_RAFT_R01.fits"});  }    Follow up:    The bug was traced to java.awt.image.BufferedImage objects not being evicted from VIS_SHARED_MEM cache.    Further search showed that java.awt.image.BufferedImage (along with java.io.BufferedInputStream) is in src/firefly/java/edu/caltech/ipac/firefly/server/cache/resources/ignore_sizeof.txt, which lists the classes that have to be ignored when calculating the size of cache.    Testing on single node server (VIS_SHARED_MEM cache is not replicated), using [host:port]/fftools/admin/status page:    BEFORE (java.awt.image.BufferedImage was commented out in ignore_sizeof.txt)    After 14 reloads:  Memory    - Used                      :      3.7G    - Max                       :     3.55G    - Max Free                  :    488.0M    - Free Active               :    488.0M    - Total Active              :     3.55G     Caches:    VIS_SHARED_MEM @327294449   Statistics     : [  Size:15  Expired:0  Evicted:0  Hits:246  Hit-Ratio:NaN  Heap-Size:1120MB  ]  OUT OF MEMORY on next reload    AFTER THE CHANGE (Commented java.awt.image.BufferedImage in ignore_sizeof.txt)    After 36 reloads:  Memory    - Used                      :   1672.9M    - Max                       :     3.55G    - Max Free                  :   1968.0M    - Free Active               :   1468.0M    - Total Active              :      3.6G    Caches:    VIS_SHARED_MEM @201164543   Statistics     : [  Size:3  Expired:0  Evicted:34  Hits:659  Hit-Ratio:NaN  Heap-Size:1398MB  ]    
Answer: 41872.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: "Implement the selected seconary index technology (see DM-2119) as a Qserv service, providing a client API to be used elsewhere in the Qserv system.  Depending on the chosen technology, this may including configuration of a separate lightweight server for the secondary index, creation of database tables, etc.  The client-side API should be technology independent."
Answer: 1354930.0

User story: "Evaluate Qserv software for the Czars and workers to identify where an interface to the secondary index will be required for efficient operation."
Answer: 192738.0

User story: "Fix type casting in obs_subaru in lates numpy in obs_subaru"
Answer: 1122.0

User story: When neither {{\--output}} or {{\--rerun}} is specified as an argument to a {{CmdLineTask}}, any output from that task appears to be written back to the input repository. Note the use of the term "appears": from a preliminary inspection of the code and documentation, it's not clear if this behaviour can be overridden e.g. by environment variables.    The HSC stack behaves differently, using {{$INPUT/rerun/$USER}} as a default output location. A [brief discussion|https://community.lsst.org/t/new-argument-parser-behavior-rerun-flag-introduction-discussion/345] suggests that this is the preferred behaviour.    Please update the LSST stack to match the HSC behaviour.
Answer: 192591.0

User story: "Back port of the following two HSC tickets:    *countInputs*  [HSC-1276|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1276]  {{meas_algorithms}}  Jul 1, 2015  [add measurement algorithm to count input images in coadd|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/51db0fd2624c7f9b641c93aa3cf6366539995d50]    {{obs_subaru}}  Sep 24, 2015  [config: activate countInputs for measureCoaddSources.|https://github.com/HyperSuprime-Cam/obs_subaru/commit/13ecd1317b05b5ff9e65fba41fe27a5cffcc2fda]    *variance*  [HSC-1259|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1259]  {{meas_algorithms}}  Jul 2, 2015  [add measurement algorithm to report background variance|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/86022f4381c3cec3f7f203b831b6a306596cfa3f#diff-7ae7aea69b58dbf075350ccfd3802cfb]    {{obs_subaru}}  Oct 19, 2015  [config: activate measurement of variance for coadds|https://github.com/HyperSuprime-Cam/obs_subaru/commit/cf1e80958bb9164dacf42d2d35a94dd366c78892]  "
Answer: 106418.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: "Add algorithms to compute the *Jacobian* correction for each object (calculable from the Wcs, but sometimes convenient)  and record the *focal plane* coordinates (instead of CCD coordinates) for sources (useful for plotting).    The standalone HSC commits to be cherry-picked are:    *Jacobian*  {{meas_algorithms}}  May 3, 2013  [Jacobian: add Algorithm to compute the Jacobian.|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/88d3bd3f32cf4d0138b80148e57bc275fc8c3454]  May 24, 2013  [Jacobian: fix up some cut/paste oversights.|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/ecad0d2559bb9815fc5560234f4502f35f50db73]  May 28, 2013  [Jacobian: fix calculation|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/7f3db53b56279929b9e416173ed09cf00dc81406]    {{obs_subaru}}  May 3, 2013  [config: enable jacobian calculation in processCcd|https://github.com/HyperSuprime-Cam/obs_subaru/commit/d0969911ee1a655fd82998f0b936fa90f443d2fd]  May 6, 2013  [config: set pixelScale for jacobian correction|https://github.com/HyperSuprime-Cam/obs_subaru/commit/e36bd1b4410812ca314f50c01f899d92acc0e7a5]      *focalplane*  {{meas_algorithms}}  May 24, 2013  [add algorithm to calculate position on the focal plane|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/dda3086f411d647e1a3e15451d7f093cd461873a]  May 25, 2013  [fix up building of focalplane algorithm|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/57d718bf51b255adf5789e389dfb776ecaa062d1]  Nov 21, 2014  [Adapt to removal of Point<float> from afw::table.|https://github.com/HyperSuprime-Cam/meas_algorithms/commit/95627d55cb7d64718a42027954474df5c3661a65]    {{obs_subaru}}  May 24, 2013  [config: activate focalplane algorithm|https://github.com/HyperSuprime-Cam/obs_subaru/commit/d999a32e7e10b25cceccc94b61890486f96c0bfd]  "
Answer: 111023.0

User story: In the default {{IsrTask}}, the variance is currently set after dark subtraction.  This means that photon noise from the dark is not included in the variance plane, which is incorrect.  The variance should be set after bias subtraction and before dark subtraction.    [~<USER> also points out (DM-4191) that the {{AssembleCcdTask}} with default parameters requires amplifier images with variance planes, even though the variance cannot be set properly until after full-frame bias subtraction.  I believe that {{AssembleCcdTask}} only requires a variance plane in the amp images because it does an "effective gain" calculation, but I suggest that this isn't very useful (an approximation of an approximation, and you're never going to use that information anyway because it's embedded in the variance plane with better fidelity).  I therefore suggest that this effective gain calculation be stripped out and that {{AssembleCcdTask}} not require variance planes.
Answer: 739287.0

User story: [HSC-1355|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1355]: "with this fix, we get much  better fringe subtraction".
Answer: 38775.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: "Evaluate results of production-scale performance tests, both single and multiple host.  Identify the technology most likely to meet requirements, and estimate performance capability with respect to those requirements"
Answer: 173341.0

User story: "Run secondary index tests across multiple hosts (server and clients), collecting performance data for production-scale indices (billions of entries, millions of queries) with many parallel queries and bulk/block updates."
Answer: 139637.0

User story: "The nightly data loader job may need to add new objectIDs, or change the chunks of existing objectIDs, _en masse_.  Develop test code (or add features to existing demonstrators) to handle bulk loading of new data to the index, or to overwrite collections of existing data.  This is significant for client-server technologies, where the bulk data may be transferred in a single transaction, with the server (possibly) handling the loop over individual elements."
Answer: 173347.0

User story: For client-server technologies (memcached, xrootd, etc.), develop multihost test jobs to exercise production-scale indices (billions of entries, millions of queries).  Index should be allocated on single "master" machine, with queries generated from one or more separate machines, possibly with multiple threads/jobs per machine.
Answer: 139646.0

User story: "Run production-scale (billions of entries) tests on different index options, collect performance statistics for allocation (CPU, memory) and for queries."
Answer: 131277.0

User story: "The method {{removeFringe}} of {{FringeTask}} is called in {{IsrTask}} but there is no {{removeFringe}}.      Not sure if {{removeFringe}} was meant to be a place holder"
Answer: 1637.0

User story: Refactor how we manage copyright and license information in stack repositories    # Identify a list of packages to process  # build and test an automated system of       - adding a global COPYRIGHT to each repo. Content will be “Copyright YYYY-YYYY The LSST DM Developers”. Years will be determined by git history.     - adding a GPLv3 license file to each repo.     - changing the boilerplate in all files to say "See the COPYRIGHT and LICENSE files in the top-level directory of this package for notices and licensing terms.” Use https://gist.github.com/ktlim/fdaea18ab3d39afdfa8e     - automatically branch, commit, merge and push    And deploy this automated system.
Answer: 50287.0

User story: "Prototype is now getting to the point where a wire-protocol package like capnproto or protobuf is needed.  capnproto is the new hotness, and we're probably going to want to migrate qserv from protobuf->capnproto at some point.    This task is to go ahead and get capnproto packaged and published for use in the replication prototype."
Answer: 1.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 {{TaskRunner.\_\_call\_\_}} fails it attempts to log a message  {code}  task.log.fatal("Failed on dataId=%s: %s" % (dataRef.dataId, e))  {code}  Unfortunately, dataRef can be a list, in which case this statement throws an exception itself and the real problem is lost.  
Answer: 20161.0

User story: See RFC-108    The only difference is that I plan to make {{\-\-show config=xxx}} be case-insensitive only if the pattern xxx is all lower-case.  If people really want to match "background" lower-case only, they can say {{--show config=xxx:NOIGNORECASE}}
Answer: 28887.0

User story: "This will be part of a wider set of test which I am hoping that Jim will fill in as additional stories under DM-1136    Basically, we hope to see how extensive a Shapelet Approximation must be done for a Psf in order to reach a stable result (stable meaning it would not markedly improve with increase in Shapelet order).    For this intial test, I propose to compare SingleGaussian, DoubleGaussian, Full, and 2 higher order models.  I will also add a model with inner and outer defined to see if those have a significant effect.  It will tell use how the existing models line up and which parameters matter.    This test will be done using the great3sims subfield organization, and with a single, randomly chosen Psf image from the 0.7 arcsec FWHM library (raw fwhm from PhoSim, the actual fwhm is closer to 0.8 arcsec)     This will probably be just the beginning of more extensive ShapeletApprox tests, so this story should be a sub-story of a larger test project which I am hoping Jim will define."
Answer: 122077.0

User story: "As a result of the new error estimation, it became apparent that a larger number of sample galaxies were required in DM-1135.  This is an expansion of that test to a larger number of galaxies.  Since the original  great3 tests had about 2 million galaxies, we should be able to do these test reasonably well with the 6 million galaxy pool created in DM-1135.  However, the measurements need to be rerun in some cases, and the error analysis done again."
Answer: 5589.0

User story: "DM-1135 mostly was inconclusive, due to the fact that the error bars were around the same size as the differences in many of the tests.  This in spite of the fact that we ran 6x as many sample galaxies as great3sims.    Investigate the reason for this, and see if we can estimate the errors more accurately.    "
Answer: 5591.0

User story: "SafeClipAssembleCoadd in HSC did not have adequate documentation, and thus neither does LSST post port. Documentation which details the functionality and usage of this function should be created, and should be available either through the [Doxygen task documentation|https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/group___l_s_s_t__task__documentation.html] or its successor . Examples of the usage and various options should also be included with the documentation."
Answer: 223170.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: "Research SUI, DAX, Butler, and Qserv authentication and authorization requirements and schemes. Document usage stories for all layers"
Answer: 1560.0

User story: "There's a stray {{pdb}} in {{CoaddDataIdContainer.makeDataRefList}}."
Answer: 11.0

User story: "Revert the temporary disabling of CModel that relates to a bug noted in DM-4033 that was causing too many failures to test that processCcd (etc.) would run all the way to completion (most of the other fixes/updates related to the initial disabling in the multiband tasks have now been completed in DM-2977 & DM-3821).     Relevant files:  {code}  config/processCcd.py   config/forcedPhotCcd.py   config/forcedPhotCoadd.py   config/measureCoaddSources.py  {code}  "
Answer: 371201.0

User story: "This was supposed to be done in Sprint 2.  The work was done, but we are still waiting on tests for ip_diffim and possibly ap before integrating to master"
Answer: 266215.0

User story: "Building boost can fail if a user-config.jam or site-config.jam exist and have options which conflict with the lsst build configuration process. Introduce a warning message if either of these files are found to notify the user."
Answer: 10035.0

User story: "LSST the Docs ([SQR-006|http://sqr-006.lsst.io]) is a system for extending our existing Jenkins build infrastructure to build Sphinx-based software documentation for our Eups-based packages. This is a ticket to implement the {{ltd-mason}} service, which runs on Jenkins after the {{buildlsstsw.sh}} step and compiles software documentation.    Specific outcomes of this ticket are    - Full specification of the YAML interface between {{ltd-mason}} and {{buildlsstsw.sh}} (including creating a mock YAML file for local testing)  - Demonstration of a Science Pipelines documentation build on a local lsstsw environment (in conjunction with content from DM-4195)  - Accommodations to the science pipelines documentation repo and documenteer for building sphinx packages are included in this ticket’s scope.    Next steps are    - Standing up the service on Jenkins and testing integration with {{buildlsstsw.sh}}  - Uploading to S3 (which involves building integration with {{ltd-keeper}}."
Answer: 202202.0

User story: "Build package documentation for {{lsst.afw}} under the new doc platform as a demonstration.    - Install a Sphinx site in lsst.afw/doc  - Implement MVP documentation pages for lsst.afw packages (table, image, etc.)  - C++ API reference from doxygen+breathe  - Python API reference from numpydoc    This ticket *will not* attempt to add new documentation content; only to show how existing content can be re-organized."
Answer: 193979.0

User story: "This task involves merging in feature branches, building Firefly standalone, tagging, push changes to github, generating changlog, and using github API to publish the release.  Release should be attached to the latest tag with downloading artifacts and changelog."
Answer: 1169.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 ticket is for implementing changes in {{obs_decam}} in order to run {{processCcd}} with raw DECam data.    Changes are mostly in {{DecamMapper}} and a new class {{DecamIsrTask}} is added. A test to retrieve defects with Butler is also added. ({{testdata_decam}} is at lsst-dev /lsst8/testdata_decam/ )    The pixels with bit 1 (bad, hot/dead pixel/column) from the Community Pipeline Bad Pixel Masks are used as bad pixels.  The CP BPM fits files are directly used as defect files. Due to their large size, they probably should not go into {{obs_decam}} repository so they are treated similarly as other calibration products.     With the changes of this ticket, the following ingest defects files into {{calibRegistry}}:  {code:java}  ingestCalibs.py . --calibType defect path-to-bpm/*fits  {code}    and the following should run past ISR:  {code:java}  processCcd.py .  --config isr.doFringe=False isr.assembleCcd.setGain=False calibrate.doPhotoCal=False calibrate.doAstrometry=False calibrate.measurePsf.starSelector.name="secondMoment"  {code}    Running fringe correction with DECam raw data will be in future tickets (DM-4223 and possibly more). Also this ticket does not cover implementing or porting new ISR functionalities that haven't yet been included in ip_isr (such as crosstalk).   
Answer: 14201.0

User story: "Outline functions and responsibilities for all parts of the L1 system"
Answer: 200847.0

User story: "Outline of data flow between Chile->NCSA and NCSA->Chile."
Answer: 143901.0

User story: "Use simple C-style array (chunk[objID], allocated up to maximum number of objectIDs), or a single-layer set of arrays (chunk[block][objID%blksize], where second index runs from 0 to size of each block) to store index compactly and provide minimum overhead for lookups."
Answer: 7078.0

User story: "Test whether xrootd could be used to serve objectId --> chunkId mapping, in particular from the performance perspective."
Answer: 44235.0

User story: "Test whether memcached could be used to serve objectId --> chunkId mapping, in particular from the performance perspective."
Answer: 27258.0

User story: The task needs to be able to specify everything that needs to be in the policy file so that the butler can put and get data for a new dataset type.    Consider that the policy data can be split between the camera-specific and the task-specific parts. (KT was thinking of calling the camera part the "genre"), this potentially reduces the amount the task has to specify.   Another option is to hard-code some some of the policy in the butler itself:  * the path template (it could be assembled out of the data id components)  **  if it's hard coded the task must pass the component dataId keys  ** if it's not hard coded the task must provide a template   * python type  * storage type    there could be user overrides too.
Answer: 2273880.0