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: "obs_monocam has some tests in it: those should get lifted into obs_base and deleted (or just deleted, if there is already an equivalent test in obs_base), and {{test_obs_monocam.py}} should be created to inherit the obs_base testing framework.    Once the new tests are merged in, the other obs packages that depend on obs_base should have their test setUp updated to reflect the new tests."
Answer: 54924.0

User story: "obs_decam has some tests in it: those should get lifted into obs_base and deleted (or just deleted, if there is already an equivalent test in obs_base), and {{test_obs_decam.py}} should be created to inherit the obs_base testing framework.    Once the new tests are merged in, the other obs packages that depend on obs_base should have their test setUp updated to reflect the new tests."
Answer: 1696535.0

User story: "obs_subaru has some tests in it: those should get lifted into obs_base and deleted (or just deleted, if there is already an equivalent test in obs_base), and {{test_obs_subaru.py}} should be created to inherit the obs_base testing framework.    Once the new tests are merged in, the other obs packages that depend on obs_base should have their test setUp updated to reflect the new tests."
Answer: 1696533.0

User story: "obs_cfht has some tests in it: those should get lifted into obs_base and deleted (or just deleted, if there is already an equivalent test in obs_base), and {{test_obs_cfht.py}} should be created to inherit the obs_base testing framework.    Once the new tests are merged in, the other obs packages that depend on obs_base should have their test setUp updated to reflect the new tests."
Answer: 1696536.0

User story: "obs_lsstSim has some tests in it: those should get lifted into obs_base and deleted (or just deleted, if there is already an equivalent test in obs_base), and {{test_obs_lsstSim.py}} should be created to inherit the obs_base testing framework.    Once the new tests are merged in, the other obs packages that depend on obs_base should have their test setUp updated to reflect the new tests."
Answer: 1695150.0

User story: in Mysql 5.7, the warning    /home/srp/lsstsw27/lsstsw/stack/Linux64/cat/12.1.rc1-3-g00b8a9c+1/python/lsst/cat/MySQLBase.py:158: Warning: Incorrect datetime value: '0000-00-00 00:00:00' for column 'executionStartTime' at row 1    is emitted.    This is because of a change in MySQL 5.7 about how '0000-00-00 00:00:00" dates are handled.
Answer: 7266.0

User story: "Add ctrl_stats to the build"
Answer: 44.0

User story: "We have new machine at ccin2p3 with fast SSD disk (SATA and NVME). This is a much better configuration for understanding performance issues in L1 prototype. Will move all testing there, for that I need usual setup - mysql and postgresql server installed with data directories either on /qserv_ssd or /qserv_nmv filesystems."
Answer: 7669.0

User story: "node_type value (master, worker, mono), are hard-coded in configuration code. This may be replaced with parameters..."
Answer: 1892949.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: "DMTN-014 and DMTN-024 describe some general technicalities and the coding guidelines for pybind11 respectively. However this information is insufficient for most developers to get started.    The scope of this story is to develop a tutorial that describes the wrapping process step-by-step. With this document + DMTN-024, and the pybind11 documentation, in hand an LSST developer should be able to wrap a package from scratch."
Answer: 109284.0

User story: "Implement individual exposure loading per item 2 on https://confluence.lsstcorp.org/display/DM/Use+Cases+for+Butler+Composite+Datasets"
Answer: 69006.0

User story: "The routine makeMosaic doesn't work if you pass in a list of images (as opposed to appending images to self)  "
Answer: 30137.0

User story: "The routine to overlay amplifier BBoxes on images, overlayCcdBoxes, mis-handles amplifiers that are flipped.  "
Answer: 11320.0

User story: "- Fix duplicate nom.tam.fits classes during build  - Add preferIPv4Stack to tomcat env.  - Add firefly.war to Firefly Standalone release page."
Answer: 153229.0

User story: "Two problems picked up by [~<USER> when trying to install 12.1:    * I broke the -P option in DM-6316 (https://github.com/lsst/lsst/issues/28)  * The help does not tell you what the default python is (https://github.com/lsst/lsst/issues/29)"
Answer: 66.0

User story: "xrootd configuration to use ( manager or server) is known at Qserv configuration time.  Nevertheless, xrootd ask for hostname at startup in order to know which config to use (manager or server). This ticket will remove this useless step by simplifying xrootd configuration.    Note that, which current Qserv setup  systems like swarm which do not expose DNS machine name via libc, cause xrootd to crash.  "
Answer: 16017.0

User story: "The conda-lsst build log for the test failure can be found here:    https://gist.github.com/<USER>dcb6ce8312aac1ff81cbb923703d8430    {code}  Running tests...  Test project /Users/square/dev/conda-lsst/miniconda/conda-bld/work/build      Start 1: test_ndarray  1/5 Test #1: test_ndarray .....................   Passed    0.01 sec      Start 2: test_views  2/5 Test #2: test_views .......................   Passed    0.01 sec      Start 3: test_ndarray-fft  3/5 Test #3: test_ndarray-fft .................***Exception: Other  0.00 sec      Start 4: test_ndarray_eigen  4/5 Test #4: test_ndarray_eigen ...............   Passed    0.01 sec      Start 5: swig_test  5/5 Test #5: swig_test ........................   Passed    0.11 sec    80% tests passed, 1 tests failed out of 5    Total Test time (real) =   0.14 sec    The following tests FAILED:     3 - test_ndarray-fft (OTHER_FAULT)  Errors while running CTest  make: *** [test] Error 8  {code}"
Answer: 56740.0

User story: "uint is not portable and should be replaced with unsigned int."
Answer: 1793510.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It has been determined that the best way to wrap afw using pybind11 is for a single developer to take one test and wrap the necessary headers. Since each test will requiring wrapping parts of multiple headers, developers working on different tests will likely need to touch the same headers and in some cases even the same classes or functions. Even using frequent rebasing is likely to lead to significant conflicts.    Note: This application does not put a real lock on the file. A developer can still edit and push changes to a file even if it is locked by another user. Instead this application serves as a tool to help minimize the number of merge conflicts while wrapping complex packages like afw.    A simple application called gitlock is being created to allow a user to create a lock on or unlock a single file from the command line, as well as display all of the currently locked files."
Answer: 101058.0

User story: Need to decide how we should be verifying that deliverables for each epic that is being marked "done" are truly done
Answer: 21709.0

User story: "DM-7049 removed at least one dataset which might be in use.    Restore any doubtful datasets to the Mappers and move them to the DM-7677 RFC.  "
Answer: 99352.0

User story: When I went to look for the pull for ctrl_orca on Monday for ticket DM-7183, I didn't see one;  I made changes to the "is True", "is False", and list(keys()) issues, and then didn't look again on Tuesday when I saw the "Review complete", so I thought it had been done, which is was not.   This is to look at those issue and fix them.
Answer: 3016.0

User story: "Create a new {{validate_base}} Stack package ({{lsst.validate.base}}), refactored from the existing measurement framework in the {{validate_drp}} package (created in DM-6629 and DM-6917).    {{validate_base}} will support a number of validation packages, including {{validate_drp}}.    Porting {{validate_drp}} to this new package will be done in a separate ticket (i.e., to merge [u/sqre/measurement-api|https://github.com/lsst/validate_drp/pull/21])"
Answer: 8537.0

User story: The NFS stack created in DM-6968 today shows an error upon initialization :    {code}  % cd  /lsst4/lsstsw/stack/  % source loadLSST.bash  setup: [Errno 13] Permission denied: '/nfs/lsst4/lsstsw/stack/.lockDir/shared-daues.801175'  You are attempting to run "setup" which requires administrative  privileges, but more information is needed in order to do so.  Authenticating as "root"  Password:  {code}    This may be occurring due to the existence of a lock and .lockDir :    {code}  %  ls -ld /nfs/lsst4/lsstsw/stack/.lockDir/  drwxr-xr-x 2 lsstsw ac 4096 Sep 19 04:49 /nfs/lsst4/lsstsw/stack/.lockDir/  % ls -ld /nfs/lsst4/lsstsw/stack/.lockDir/*  -rwxr-xr-x 1 lsstsw ac 0 Sep 14 00:36 /nfs/lsst4/lsstsw/stack/.lockDir/shared-lsstsw.2531683  {code}    Could this be investigated ?                  Greg   
Answer: 17558.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 ndarray pybind11 support can live alongside the swig (and boost python) code in upstream.  Move these changes upstream and use the new version in the stack (with pybind11 disabled for now).    Note that this ticket includes making some small changes to {{afw}} and potentially other stack packages as well due to non-swig-specific ndarray header files moving from {{swig/}} to {{converter/}}."
Answer: 18646.0

User story: "Currently, it lives as all the scripts starting with {{hsc}} in branch {{u/<USER>working}} of {{pipe_tasks:bin.src}}. These should all move to a new package in the lsst-dm organization."
Answer: 300.0

User story: lsst.pipe.tasks.mocks.mockCoadd.MockCoaddTask is initialized with    {code:python}  self.objectIdKey = self.schema.addField("objectId", type=long, doc="foreign key to truth catalog")  self.exposureIdKey = self.schema.addField("exposureId", type=long,                                            doc="foreign key to observation catalog")  {code}    When attempting to set fields in a new catalog with  {code:python}  simSrcRecord = simSrcCatalog.addNew()  simSrcRecord.setL(self.objectIdKey, truthRecord.getId())  {code}    the following error is given:  {code}  TypeError: in method 'BaseRecord_setL', argument 2 of type 'lsst::afw::table::Key< std::int64_t > const &'  {code}    This error only occurs in python 3 when trying to use a long, which is really a wrapper for int. Using setI works but truncates the integer to 32 bits, which is unacceptable. See    https://github.com/lsst/pipe_tasks/blob/master/python/lsst/pipe/tasks/mocks/mockCoadd.py#L170-L201  https://github.com/lsst/pipe_tasks/blob/master/python/lsst/pipe/tasks/mocks/mockCoadd.py#L112-L131    for the relevant code.
Answer: 1795542.0

User story: "The metrics app requires 'persistent' test data in order to test features like data set selection,  annotations display, etc. This should be distinguished from the unitests that we run with py.test, unitests can still load data but in a database that is created only for that and destroyed after the tests (using django test framework for instance).    The right mechanism for that seems to be a fixture with test data that can be loaded locally or at a dev instance deployed at AWS."
Answer: 1465.0

User story: "Begin the visualization documentation process.  This is the first step of probably much more documentation.  However, some needs to be put into jsdocs soon so this ticket should be that documentation."
Answer: 8.0

User story: "Based on L2 ConOps and consider the process flow of a campaign processing in Batch Production Services, draw a swimlane diagram to illustrate and clarify a simplified scenario of campaign processing.     "
Answer: 21220.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-7049, an set of datasets were moved from the HSC mapper to daf_butlerUtils.  These are in exposures.yaml and datasets.yaml, and are now available to all cameraMapper subclasses (provided that there is an exposures or datasets section in their own Mapper.paf file.)    An RFC will be published for each Mapper describing possible additional changes:    1.  Additional cleanup is required in each of the obs_*/policy/*Mapper.paf files to fully implement this move.  Datasets which are not consistent with the new "shared" datasets need to be altered before they can be removed, but carefully, so as not to disturb the code which utilizes the mapper.    2.  Identify datasets in each mappers which have the same function as a shared dataset, but a different name.  If possible, these should be renamed and made consistent with the shared dataset.    3.  Attempt discover datasets which are no longer in use and could be deleted.
Answer: 48791.0

User story: "Need to define policy about giving access to Confluence/JIRA to people closely collaborating with us (eg, collaborators at UK)"
Answer: 747309.0

User story: "Previously we made every T/CAM a community.lsst.org admin so that they could add their team members to the LSST and LSSTDM groups to access private community categories.    Discourse now has the concept of Group owners, who can add/remove members from individual groups.    I’d like to limit the number of people with Admin credentials since it poses a security risk; especially considering our responsibility to support private Science Collaboration categories.    This ticket will update community configurationg and Developer Guide documentation to implement this."
Answer: 258.0

User story: "F16 Service Management ~ monthly."
Answer: 104373.0

User story: "F16 Service Management ~ monthly."
Answer: 61950.0

User story: "F16 Service Management ~ monthly.  "
Answer: 16301.0

User story: "Switch the logging/tracing in C++ from lsst.pex.logging to lsst.log in meas_algorithms"
Answer: 13465.0

User story: "Implement RFC-224."
Answer: 123287.0

User story: "Implement RFC-223."
Answer: 22057.0

User story: "Implement RFC-222."
Answer: 1094728.0

User story: "Conda changed the location of channel_alias with 4.2.6. See:    https://github.com/conda/conda/blob/master/CHANGELOG.md#426-2016-09-14 https://github.com/conda/conda/pull/3410/commits    The initial fix appears to be use conda.config.context.channel_alias instead of conda.config.channel_alias."
Answer: 75875.0

User story: "As we search and display the LSST sources/objects, the SUIT should be able to choose a sensible background image to overlay the sources/objects on.     We need to come up with a strategy and the potential images to choose from at different stages:  *  PDAC v1 (end of F16): Current method that Firefly employs to choose. Depending on size needed, it will pick one from 2MASS, WISE, SDSS, IRAS.   * PDAC v2 (end of S17)  * Ready ComCAM  "
Answer: 1159286.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 covers work to systematically onboard all science collaborations onto Community:    - The 'Science' category will remain a completely public category.  - A new 'Science Collaborations' category will be visible to all members of an LSST science collaboration. The hope is that many discussions can happen here outside the silos of individual collaborations. We can still tag discussions here to make it easy to find TVS-oriented discussions, for example.  - Each science collaboration will get at least one private subcategory inside 'Science Collaborations' for internal collaboration business (equivalent to what I've set up for TVS).  - New topics from the individual science collaboration categories will be forwarded to the collaborations' original email lists with the mailbot service.  - Science collaborations will be systematically invited and incorporated into the appropriate groups.  - Welcome document.    This work is being coordinated with Lucianne Walkowicz."
Answer: 63454.0

User story: "The talk is archived at https://zenodo.org/record/153867#.V92VODvsXPg and was given on September 12, 2016."
Answer: 9.0

User story: "Unit test {{testOpenFiles.py}} failed on my Ubuntu 14.04 system.  The subroutine {{getOpenFiles}} required {{/usr/sbin/lsof}}, which was not on my system.  There was a {{/usr/bin/lsof}}, so I was able to get the unit test to work by adding a soft link."
Answer: 5195.0

User story: When preConvolve is set to True in imageDifference.py, the resulting diffim is actually a likelihood image which can be used directly for detection, but it is not entirely clear how measurement is supposed to work on this image. Under the assumption that all DiaSources are point-sources, the PeakLikelihoodFlux plugin can be used for flux measurement, but we would also like centroids and (if possible) shapes. Furthermore, the dipole measurement algorithm (both old and new) uses the diffim's PSF to model dipoles; however this will not be accurate in the "pre-convolved" diffim. Instead, we will need to use the PSF convolved with itself. Or we might just want to fall back on a more simple dipole measurement like the original naive (weighted moments) algorithm.    This is probably worthy of an RFC.
Answer: 1800852.0

User story: "It was decided that to correctly evaluate and understand preconvolution, we need to implement the decorrelation in the case when preconvolution is enabled. This was derived and described by [~<USER> in his presentation at the 2016 JTM and summarized in DMTN-021 as part of DM-7466. For this ticket, we will implement the *static* decorrelation kernel. This will be extended to the spatially varying kernel in DM-7611."
Answer: 20425.0

User story: "When moving {{ndarray}} to an external package some LSST package dependencies and scons specific things were left in files in the {{ups}} directory. This is a ticket to clean them up."
Answer: 2588.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: "{{astrometryNetDataConfig.py}} gained a {{from past.builtins import execfile}} during the python3 conversion. We should replace this with a more modern syntax."
Answer: 895879.0

User story: "Some of the packages that have been ported to python 3 do not declare their dependency on {{python_future}}. Trivial fixes included on this ticket."
Answer: 55.0

User story: Allow null values to display as "null", currently a value of null is left blank. 
Answer: 7148.0

User story: "Support pytest."
Answer: 859782.0

User story: "Support pytest."
Answer: 495416.0

User story: "Support pytest."
Answer: 856827.0

User story: "Support pytest."
Answer: 555868.0

User story: "Update the tests to work with pytest."
Answer: 475105.0

User story: "Update {{testGetPsf.py}} to work with pytest."
Answer: 27068.0

User story: "In {{lsstsw}} we currently force {{miniconda2}} version to 3.19.0 and {{miniconda3}} to 4.0.5.    After deploying {{miniconda2}} we get:  {code}  $ otool -L miniconda/lib/libpython2.7.dylib   miniconda/lib/libpython2.7.dylib:   libpython2.7.dylib (compatibility version 2.7.0, current version 2.7.0)   /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.0.0)   /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 476.0.0)   /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)  {code}  Doing {{conda update python}} results in:  {code}  python:      2.7.11-0     --> 2.7.12-1  {code}  and:  {code}  $ otool -L miniconda/lib/libpython2.7.dylib   miniconda/lib/libpython2.7.dylib:   @rpath/libpython2.7.dylib (compatibility version 2.7.0, current version 2.7.0)   /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 159.1.0)   /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 635.21.0)  {code}  which gives the correct use of {{@rpath}} without us having to manually modify it (which we stopped doing a while back). This is important because Mac OS X builds break with {{galsim}} on XCode 8 if the {{@rpath}} is missing.    Updating our miniconda versions to v4.1.11 fixes the problem, although we will need to update our pinned package versions after making this change as currently without the {{-b}} option the 2.7.12 fixed python is installed and then immediately downgraded.    4.1.11 is needed for both miniconda2 and miniconda3.    The workaround for mac users is to run {{conda update python}} before building {{galsim}}."
Answer: 139705.0

User story: "Install GPFS on LSSTdev servers to prepare for data migration."
Answer: 41868.0

User story: "The tests in {{shapelet}} need to be modernized to support pytest and to drop {{suite}}."
Answer: 488000.0

User story: "Modernize the test file to be compatible with pytest."
Answer: 90.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 services layer with methods to access the API - this will make the metrics bokeh app easier to read and all methods to access the API can be organized in the same file (services.py) shared by the bokeh apps."
Answer: 2926.0

User story: "We have not implement the target panel resolve option.  When is there in the search panels now are dummy ui components."
Answer: 125.0

User story: "Produce a test data repo  to be used for the same purposes at -cfh_testdata-  {{validation_data_cfht}}"
Answer: 210164.0

User story: "The lsst.cat package has a reference to file(), which is not supported in Python 3.  Updating this to use open()."
Answer: 1633.0

User story: "Add attribute to the extra phase column so a comment or some description appears in the ipac table header when is saved by the user if possible    NOTE: this ticket is combined with DM-7594."
Answer: 2572.0

User story: "Now that DM-7165 is done, use the code in the LC handler to complete the processor added [DM-7162]"
Answer: 2985.0

User story: "After the SUIT requirements's approval by TCT, we need to put them in the Enterprise Architect. "
Answer: 476566.0

User story: "Review, revise, and submit for approval of the SUIT requirement documents."
Answer: 94021.0

User story: "SUIT vision document work, review, revision, and submission for approval by TCT. "
Answer: 94034.0

User story: "Version 3.2 of MPICH fails multiple tests on OS X and does not integrate well with mpi4py. Presently the newer 3.3a development version performs better and when the stable version 3.3 is released we should upgrade the stack."
Answer: 717426.0

User story: "The new {{lsst_py3}} metapackage enumerates eups products known to be compatible with python3.  A new dedicated jenkins job has been requested to catch regressions."
Answer: 79.0

User story: [This notebook|https://github.com/lsst-dm/diffimTests/blob/master/20.%20compare%20photometry-corrected-many-DECam-images.ipynb] (and [this one|https://github.com/lsst-dm/diffimTests/blob/master/20.%20compare%20photometry.ipynb] too) suggest that flux measurement is not being "conserved" by the decorrelation (i.e., it is about 10% lower). This appears to be a bug. This needs to be verified, and if it still appears to be true, understand why and fix it.
Answer: 191.0

User story: "These tiger teams are intended to be responsible for the design, creation and maintenance of user guides and operations manuals for *every Data Management software project, service/platform and data product.* This ticket is to found these tiger teams by    # Identify all Data Management products that need user guides  # Populate a tiger team for each product with _at least_ one each: a T/CAM who can schedule work, subject matter experts, and a documentation engineer (i.e., myself)."
Answer: 1247.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: "Draft and implement language in the DM Python Style Guide that reflects the consensus of RFC-97 (PEP 8, aka underscore naming). Specifically:    # Existing non-public APIs and variables MAY be switched immediately to PEP 8 naming  # New APIs (or is it entire new EUPS packages?) SHOULD use PEP 8 naming  # Existing public APIs that have no upstream consumers SHOULD be switched to PEP 8 naming  # Existing public APIs that are consumed MUST NOT be changed, pending imlementation of a migration process"
Answer: 293383.0

User story: "To support broad testing of obs packages, with minimal configuration, we will add an {{obs_base}} package that all obs packages will depend on. It will contain a test suite for them to derive from, plus frameworks for other modules (e.g. {{makeSomeCameraRepository.py}}).    {{obs_test}} will be the demo for how this new module works. Implementation details will be worked out along the way."
Answer: 76646.0

User story: "With the implementation of RFC-203  --logdest option was removed from command line tasks.    validate_drp is using that, see  for instance https://ci.lsst.codes/job/validate_drp/dataset=cfht,label=centos-7,python=py2/309/console  "
Answer: 952.0

User story: "The current logic to set detection.thresholdValue to 5.0 if doDecorrelation == True is set in setDefaults(), and so never runs. This block needs to be moved elsewhere (doValidate, perhaps?) so that it runs correctly."
Answer: 169.0

User story: "Produce initial draft of LDM-493 outlining core concepts:    - taxonomy of documentation  - guidelines on what kinds documentation goes where  - implementation policies (formats)"
Answer: 69177.0

User story: "Discourse has a new capabilility of assigning non-admins as ‘owers’ of groups. This is an ideal workflow to T/CAMs. We should update https://developer.lsst.io/getting-started/onboarding.html to reflect this new onboarding procedure."
Answer: 16317.0

User story: "coding/cpp_style_guide.rst has the line:    bq. Instructions for using devtoolset-3 to obtain a more modern gcc on the LSST cluster machines: https://confluence.lsstcorp.org/display/LDMDG/Developer+Tools+at+NCSA#DeveloperToolsatNCSA-AlternateDevelopmentEnvironment.    The new URL is https://developer.lsst.io/services/lsst-dev.html#select-appropriate-developer-tools"
Answer: 62.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 a mapper is specified to the butler as a dot-delimited string (i.e. the module is part of the mapper specification), the importer fails. For example if you use   {code}  RepositoryArgs(mapper='lsst.daf.persistence.CameraMapper')}}  You get the output  {{Traceback (most recent call last):    File "tests/testImportMapper.py", line 52, in test      butler = dafPersist.Butler(outputs=repositoryArgs)    File "/Users/n8pease/2/lsstsw/build/daf_persistence/python/lsst/daf/persistence/butler.py", line 285, in __init__      self._addRepo(args, inout='out', defaultMapper=defaultMapper, butlerIOParents=butlerIOParents)    File "/Users/n8pease/2/lsstsw/build/daf_persistence/python/lsst/daf/persistence/butler.py", line 382, in _addRepo      repo = Repository(cfg)    File "/Users/n8pease/2/lsstsw/build/daf_persistence/python/lsst/daf/persistence/repository.py", line 88, in __init__      self._initMapper(repositoryCfg)    File "/Users/n8pease/2/lsstsw/build/daf_persistence/python/lsst/daf/persistence/repository.py", line 108, in _initMapper      module = __import__(module)  ImportError: No module named CameraMapper  {code}  The module that contains the CameraMapper ({{lsst.daf.persistence}}) should be imported, not the module+class name.
Answer: 66612.0

User story: "A few packages use pex_logging but do not explicitly specify so in their ups files (either .table or .cfg). Please add them.    - cat  - coadd_utils  - ip_diffim  - meas_extensions_photometryKron  - meas_astrom  "
Answer: 92.0

User story: "Using the    - Understanding developed in DM-7561;  - Dependency map developed in DM-7557;  - Responsibility assignments developed in DM-7031;  - Rough resource requirements developed in DM-7032, DM-7034;  - Tooling decided in DM-7559;    develop an outline of a plan for Data Release Production.  "
Answer: 34836.0

User story: "Participate in the meeting called by [~<USER>:    {quote}          Just confirming we’ll meet for an initial planning meeting tomorrow at 10am PT. Roughly, the goal is to make sure we’re on the same page on the principles for the deployment plan you guys have    started developing, and to begin putting together a Gantt chart and milestones for what we believe thePipelines groups will deliver (and need) based on what we know is in LDM-151.  {quote}"
Answer: 469.0

User story: "Detailed read-through of the CPP section of LDM-151. Identify areas of uncertainty, resolve them with stakeholders (ie, [~<USER>, at least initially). Make copious notes."
Answer: 67540.0

User story: "Start trying to think through the replan using OmniPlan. Is it useful? If not, are there alternative technologies that would be better?"
Answer: 6618.0

User story: "Identify the relationships that the Calibration Products Pipeline have with other parts of LDM-151 (chiefly algorithmic components) and with external deliverables, and record these appropriately."
Answer: 67547.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: "Identify the relationships that the various DRP pipelines have with other parts of LDM-151 (chiefly algorithmic components) and with external deliverables, and record these appropriately."
Answer: 478.0

User story: Please add {{lsst_ci}} to the default product list (along with {{lsst_distrib}} and {{lsst_sims}}) to make it clear that {{lsst_ci}} is going to be built by default. Revert the "Skip Demo" behavior to the old behavior prior to DM-5433, of running the stack demo or not running the stack demo (which only requires {{lsst_apps}} to be built). The current situation has caused much confusion.    This ticket was initially a request to make it clear in the text associated with "Skip Demo" that choosing the demo will cause {{lsst_ci}} to be built.    
Answer: 1056695.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: "Changes to plugin linking have been made upstream in XRootD (plugins now to link against import library).  This ticket is to update the lsst-dev XRootD branch from upstream and make the necessary parallel change to the Qserv build scripts."
Answer: 1231.0

User story: "Download, compile, install Piff. Figure out how it works (or doesn't). Start familiarizing yourself with the codebase."
Answer: 46903.0

User story: "Routine refresh of lsst-technote-bootstrap:    - Update requirements.txt to be consistent with new documenteer stack  - Update travis.yaml to be consistent with modern usage of LSST the Docs  - Support LDM documents"
Answer: 14180.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: "An empty column seems to be visible on the right-hand side of a table when no description is available in option panel of the XY-plot column setting, table option and fits header table."
Answer: 12810.0

User story: "   Analogous to the work of   DM-6968 for NFS, we request a shared stack within the GPFS file system for  lsst-dev7 and the Verification Cluster (48 nodes, 1152 cores).       The familiar NFS home directories are available on the front end system lsst-dev7, but are not mounted on the compute nodes of the Verification Cluster.  As such, the NFS stack of DM-6968 is not usable for computation on the Verification Cluster.    Initial testing shows computation against a stack in GPFS can execute at least 300+ simultaneous tasks/pipelines without significant slowdown, suggesting a wide range of work can be performed with a stack in the shared GPFS space on the >~ 1000 cores of the Verification Cluster.    The suggested location for the GPFS stack  is under  /software/lsstsw , reachable on lsst-dev7 (i.e., the build of the stack would be done on lsst-dev7, running CentOS 7.2.1511 ).    The /software space is considered a location where various reference software stacks might be made available to the team.    In addition to /software/lsstsw , the 'lsstsw' user does have a 'GPFS home' directory /gpfs/fs0/home/lsstsw  that could also be used, though the organization offered by /software appears preferable.    (The 'lsstsw' user  would continue to have a home directory in NFS for the time being, with an eventual transition to that on GPFS. )"
Answer: 11268.0

User story: "In preparation for integrating the Forward Global Calibration Module code with LSST, we'd like to get a feeling for the abstractions and data structures it uses which can be replaced with (perhaps extended versions of) LSST equivalents. Please identify likely candidates, so we can discuss/demo the LSST equivalents. Examples might include filters, camera geometry, etc."
Answer: 914409.0

User story: "Renew *.lsst.org certificate and install on community.lsst.org. Procedure at https://meta.discourse.org/t/allowing-ssl-https-for-your-discourse-docker-setup/13847"
Answer: 681.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 seems to be multiple problems, but here's one:  {code}  pprice@tiger-sumire:~ $ setup -t w_2016_35 lsst_distrib  pprice@tiger-sumire:~ $ python -c 'import lsst.meas.extensions.shapeHSM'  Traceback (most recent call last):    File "<string>", line 1, in <module>    File "/tigress/HSC/LSST/stack/Linux64/meas_extensions_shapeHSM/12.0-1-g63326a6+1/python/lsst/meas/extensions/shapeHSM/__init__.py", line 23, in <module>      from lsst.meas.base import BasePlugin, wrapSimpleAlgorithm    File "/tigress/HSC/LSST/stack/Linux64/meas_base/12.0-9-g5a8b194+2/python/lsst/meas/base/__init__.py", line 2, in <module>      from .pluginRegistry import *    File "/tigress/HSC/LSST/stack/Linux64/meas_base/12.0-9-g5a8b194+2/python/lsst/meas/base/pluginRegistry.py", line 29, in <module>      import lsst.pipe.base    File "/tigress/HSC/LSST/stack/Linux64/pipe_base/12.0-8-gfd1563d+6/python/lsst/pipe/base/__init__.py", line 2, in <module>      from .argumentParser import *    File "/tigress/HSC/LSST/stack/Linux64/pipe_base/12.0-8-gfd1563d+6/python/lsst/pipe/base/argumentParser.py", line 41, in <module>      import lsst.utils    File "/tigress/HSC/LSST/stack/Linux64/utils/12.0-9-gf85c792/python/lsst/utils/__init__.py", line 24, in <module>      from .utilsLib import *    File "/tigress/HSC/LSST/stack/Linux64/utils/12.0-9-gf85c792/python/lsst/utils/utilsLib.py", line 107, in <module>      import lsst.pex.exceptions.exceptionsLib    File "/tigress/HSC/LSST/stack/Linux64/pex_exceptions/12.0-1-g4e7a85b+2/python/lsst/pex/exceptions/__init__.py", line 24, in <module>      from .wrappers import *   # this intentionally overrides all the C++ exception types    File "/tigress/HSC/LSST/stack/Linux64/pex_exceptions/12.0-1-g4e7a85b+2/python/lsst/pex/exceptions/wrappers.py", line 2, in <module>      standard_library.install_aliases()    File "/tigress/HSC/LSST/stack/Linux64/python_future/0.15.2+1/lib/python/future-0.15.2-py2.7.egg/future/standard_library/__init__.py", line 483, in install_aliases      import test    File "test.py", line 2, in <module>      import lsst.afw.table as afwTable    File "/tigress/HSC/LSST/stack/Linux64/afw/12.0-23-ga0b5675/python/lsst/afw/table/__init__.py", line 1, in <module>      from .tableLib import *    File "/tigress/HSC/LSST/stack/Linux64/afw/12.0-23-ga0b5675/python/lsst/afw/table/tableLib.py", line 756, in <module>      import lsst.afw.geom.geomLib    File "/tigress/HSC/LSST/stack/Linux64/afw/12.0-23-ga0b5675/python/lsst/afw/geom/__init__.py", line 25, in <module>      from .geomLib import *    File "/tigress/HSC/LSST/stack/Linux64/afw/12.0-23-ga0b5675/python/lsst/afw/geom/geomLib.py", line 4504, in <module>      class SingularTransformException(lsst.pex.exceptions.exceptionsLib.RuntimeError):  AttributeError: 'module' object has no attribute 'exceptions'  {code}
Answer: 823.0

User story: "Please make a list of JS source files that need JSDoc content updated in order to generate the JSDoc for Firefly JS API.     The update of all the source files will be separate tasks. "
Answer: 1147.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: About one time in ten {{testBox.py}} fails:  {code}  $ python tests/testBox.py   .E................  ======================================================================  ERROR: testConstruction (__main__.Box2DTestCase)  ----------------------------------------------------------------------  Traceback (most recent call last):    File "tests/testBox.py", line 292, in testConstruction      self.assertFloatsAlmostEqual(box.getDimensions(), geom.Extent2D(abs(dim.getX()), abs(dim.getY())))    File "/Users/timj/work/lsstsw3/stack/DarwinX86/utils/12.0-10-g3b62a7d+1/python/lsst/utils/tests.py", line 636, in assertFloatsAlmostEqual      for a, b, diff, rel in zip(lhs[bad], rhs[bad], absDiff[bad], relTo[bad]):    File "/Users/timj/work/lsstsw3/build/afw/python/lsst/afw/geom/geomLib.py", line 2113, in __getitem__      if k < 0 or k >= 2: raise IndexError(k)  ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()    ----------------------------------------------------------------------  Ran 18 tests in 0.038s    FAILED (errors=1)  {code}    Turns out that the random seed setting was moved from module level to class level but only one of the classes was fixed.  
Answer: 25.0

User story: This is the implementation ticket for RFC-205.    The suggested additional text is given below, which probably best fits as a subsection of section 10 of the python style guide:    Code must not be placed inside `if False:` or `if True:` blocks, nor left commented out. If one has debugging code or if one is undecided about which particular implementation to use, such code must be placed inside a "named" `if` statement. Such blocks may have a comment describing the conditions under which said code can be removed (e.g. completion of a ticket, a particular date). For example, for code that will likely be removed in the future, once testing is completed:    {code}  # Delete old_thing() and this "if" once we have all the unittests in place (DM-123456).  use_old_method = False  if use_old_method:      old_thing()  else:      new_thing()  {code}    Such debugging flags should usually be lifted up into the method's keyword arguments to allow users to decide which branch to run. For example:    {code}  def foo(x, debug_plots=False):      do_thing()      if debug_plots:          plot_thing()  {code}    or, using [lsstDebug|https://lsst-web.ncsa.illinois.edu/doxygen/x_masterDoxyDoc/base_debug.html], which can be controlled as part of a commandline task:    {code}  import lsstDebug  def foo(x):      do_thing()      if lsstDebug.Info(__name__).debug_plots:          plot_thing()  {code}
Answer: 180091.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: "At some point in the past week or so failures from Jenkins have stopped making available the output of test {{.failed}} files or the output of the {{_build.log}} file. This makes is almost impossible to work out why Jenkins failed.    Examples: https://ci.lsst.codes/job/stack-os-matrix/label=centos-6,python=py2/15505//console and from last week: https://ci.lsst.codes/job/stack-os-matrix/label=centos-6,python=py2/15194//console"
Answer: 1523.0

User story: "When there's no data available, {{BatchTaskRunner}} falls over because {{log}} is a module rather than a logging object."
Answer: 1085.0

User story: "LCR-403 (among other things) made official the satellite processing center at CC-IN2P3, but its presence and use has not been consistently written into the DM design documents.  The following documents need to be checked to see if changes are needed, have any such changes implemented, and have new versions recommended by the TCT and baselined:  * LDM-129  LSST Data Management Infrastructure Design  * LDM-152 LSST Data Management Middleware Design  * LSE-78 LSST Observatory Network Design  * LDM-142 LSST Network Sizing  * LDM-148  LSST Data Management Sytem Design  "
Answer: 1008407.0

User story: "Implement RFC-212."
Answer: 4.0

User story: The star selector produces many warnings of the type:  {code}  lsst::pex::exceptions::LengthError: 'Box2I(Point2I(-6,882),Extent2I(41,41)) doesn't fit in image 2048x4176 {0}; Extracting image of PSF candidate {1}'    singleFrameDriver.processCcd.charImage.measurePsf.starSelector WARNING: Failed to make a psfCandidate from star 36716867959652611:     File "src/image/Image.cc", line 92, in static lsst::afw::image::ImageBase<PixelT>::_view_t lsst::afw::image::ImageBase<PixelT>::_makeSubView(const Extent2I&, const Extent2I&, const _view_t&) [with PixelT = float; lsst::afw::image::ImageBase<PixelT>::_view_t = boost::gil::image_view<boost::gil::memory_based_2d_locator<boost::gil::memory_based_step_iterator<boost::gil::pixel<float, boost::gil::layout<boost::mpl::vector1<boost::gil::gray_color_t> > >*> > >; lsst::afw::geom::Extent2I = lsst::afw::geom::Extent<int, 2>]      Box2I(Point2I(-4,1601),Extent2I(41,41)) doesn't fit in image 2048x4176 {0}    File "src/PsfCandidate.cc", line 200, in std::shared_ptr<lsst::afw::image::MaskedImage<EntryT> > lsst::meas::algorithms::PsfCandidate<PixelT>::extractImage(unsigned int, unsigned int) const [with PixelT = float]      Extracting image of PSF candidate {1}  {code}    The exceptions that produce these are very much expected (we haven't restricted the x,y range of the candidates, and so some will be near the edge of the image) so downgrade from a warning to debugging output.
Answer: 168.0

User story: "Please remove the {{\--id field=...}} and {{\--calibId calibVersion=...}} parameters from these tasks, as they should be trivially derivable from the other parameters."
Answer: 1806725.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 ticket branch for DM-6168 has diverged quite a bit due to the massive changes to unit tests and the Python 3 conversion work that affects {{%pythoncode}} sections in the swig files. This ticket aims to rebase the pybind11 changes on top of those."
Answer: 46004.0

User story: "The {{log}} package was recently added as a future replacement for {{pex_logging}}.  Wrap this package with pybind11 instead of swig."
Answer: 41957.0

User story: "Symptom: jobs are returned in the wrong order from the job api endpoint     Cause: ordering is done by 'ci_id' which is a CharField in the Job model, fix that to have proper  numerical ordering when returning jobs from the API. Write a test for that.  "
Answer: 7125.0

User story: "When testing DM-7514 I realized that DM-7260 broke one of the tests (reversed the assert sense). This ticket fixes that and also reverts the {{next()}} method to {{next()}} function conversion (see DM-7323)."
Answer: 1034.0

User story: "While investigating DM-7509 concerning {{obs_sdss}} it was noticed that the tests skip when {{lsst-db.ncsa.illinois.edu}} was not available. This reminded me that we also use hosts {{lsst10.ncsa.uiuc.edu}} ({{daf_persistence}} and {{ctrl_orca}}) and {{lsst10.ncsa.illinois.edu}} (in {{cat}}).    Are all 3 of these the same system? If so, which one is canonical? My login credentials definitely work for {{lsst-db}} and {{lsst10}}."
Answer: 7087.0

User story: "We need to add JSDoc generation in Jekins build and bundle it in the firefly.war file when we make Firefly release.  "
Answer: 8730.0

User story: "Port of [HSC-1419|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1419]."
Answer: 6932.0

User story: "This ticket is for eslint updates to JS Doc.    We need to   1. make sure eslint checks jsdoc  2. minimize error output (like missing parameter descriptions or return tag for function that have no return)"
Answer: 8823.0

User story: "Based on the discussions from DM-7503, the desired functionality from DM-7504 and the new {{Footprint}} design from DM-3559, come up with a high-level design for the refactored deblender. Discuss it with the stakeholders (RHL, Jim, John) and make sure that everybody is happy."
Answer: 339854.0

User story: As part of DM-3622, we aim to make the single-band deblender equal to "the state of the art". What does this mean in practice? Compile a list of features we need to add (the SDSS anti-shredding algorithm is the canonical example; are there others?) and pathological behaviour that we need to fix. Ensure they're all programmed into the epic as stories.
Answer: 77736.0

User story: "Chat with stakeholders in the deblender (at least RHL, <USER> to get a better feeling for their vision of how it should be developed in the future. Understand the architectural requirements for multi-band deblending."
Answer: 40233.0

User story: "Some individual logging in coadd_utils and coadd_chisquared uses lsst.pex.logging. Switch from lsst.pex.logging to lsst.log there."
Answer: 29083.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: We need to define a process that will ensure we properly check quality of epics that are marked "Done". That includes checking if all deliverables are present (eg code written and linked to the epic), the code is properly documented, unit tests are available etc.
Answer: 685219.0

User story: "Merge in changes from <USER>conda-lsst.    This is already merged into my branch but needs to be reviewed and merged before my changes are PRed."
Answer: 9959.0

User story: "Begin loader runs to ingest staged catalog data to PDAC"
Answer: 119655.0

User story: "Study the existing storage model so improvements/updates can be scoped/planned."
Answer: 1197793.0

User story: " Address butler configuration for imgserv to it can access calexps within PDAC  "
Answer: 130754.0

User story: "Igor has located calexps, and begun work to stage them to NCSA.  Figure out final location in PDAC needed to support imgserv, transfer images there, and drop duplicates."
Answer: 71813.0

User story: "A bunch of new requirements to Supertask comes from Production system designed currently by NCSA (DM-7678).    Understand these requirements and try to think how they map into new interface between Supertask and Production system."
Answer: 96237.0

User story: "Review the existing sizing model.  What is needed?  (Should the model be built differently, or does the model itself need extension/revision, or is all that is required to update tech forecast curves, etc.)"
Answer: 390361.0

User story: "Per discussion on Sept 1st ([mtg note here|https://confluence.lsstcorp.org/display/DM/Meeting+About+Documentation+2016-09-01]), we shoulid coordinate defining policies related to google docs and ensure they are clearly documented. Main issue: stories/epics are closed, they point to google docs that are scattered at random places. Google docs are fine for collaborative doc writing, but official/final versions should be transferred to official DM repositories"
Answer: 318474.0

User story: "Per discussion on Sept 1st ([mtg note here|https://confluence.lsstcorp.org/display/DM/Meeting+About+Documentation+2016-09-01]), we should revisit LDM docs:  * produce a map of top level docs (flow down is not always good)  * revisit scope of what is covered in which doc (example, not clear if LDM-151 is just for design, or for scoping/resource loading as well)"
Answer: 391519.0