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: "Take a look at the (static) plots which are being produced by the DRP group's tooling as part of regular HSC RC2 reprocessing (see https://confluence.lsstcorp.org/display/DM/Reprocessing+of+the+HSC+RC2+dataset for output locations). Understand what plots are available. Think about how they might be relevant to AP, or how something similar might be relevant to AP.    Ultimately, let's discuss with [~<USER> if we can schedule a brown bag about this."
Answer: 232139.0

User story: " SNFactory collaboration in Button et al 2012 ([https://arxiv.org/pdf/1210.2619.pdf]) reported the determination of atmospheric parameters from the analysis of ~3000 spectra taken with the SNIF instrument installed on the UH telescope at Mauna Kea, Hawaii.    The result is inconclusive/not so convincing.    As they were not using radiative transfer simulation nor Satellite data, they propose to deliver the spectra and I would redo the last step of the analysis using LibradTran and Nasa Merra-2 data.          "
Answer: 120985.0

User story: "We want to answer this question :   * What is the sensitivity of calibrated magnitudes to non-gray components of atmosphere ?     My contribution consists in providing realistic atmospheric condition .    Here is an illustration of PWV in 2017 at LSST site          !pwv2017.png!         !pwv1year.png!         I now have to find representative distributions for the other parameters. "
Answer: 378147.0

User story: "The objective is to assess the validity of the axis-symmetry traditional hypothesis...  Which is quite wrong :    !Capture d’écran 2018-03-30 à 17.35.11.png!"
Answer: 121053.0

User story: "After some discussion with [~<USER>, we agreed it's probably easiest for us to just do the sphinx setup for all the packages ourselves (it takes me longer to teach someone how to do a package than to just do it; SublimeText makes the file editing very fast). I'll tackle as many as I can now, and leave the rest for [~<USER>. I'll track the ones I'm doing on the confluence page:    https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73573930    I won't do anything with any packages that are already claimed on there: someone will have to bug folks to merge what they've got, if they haven't already.    Note that this won't entail any actual numpydoc conversion: that is left for others."
Answer: 22975.0

User story: "Write high level bullet points for new functionality in v15.0 release."
Answer: 10030.0

User story: "[~<USER> wants to visualize maps of astrometric repeatability to help test jointcal.  Make a notebook demonstrating how {{qa_explorer}} can do this."
Answer: 615543.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 the current irsadev version of the HiPS viewer, it appears that the FOV display is either in degrees or in arcseconds, represented by the '°' and '"' symbols, respectively.  It does not have an intermediate display of arcminutes.  Before we go on to apply this to all image viewers, not just HiPS, we should agree on what we want.    Personally I would go for adding the intermediate layer.  I find it a bit odd to see " 2711" " as a field of view, instead of " 45' ".  Also in other Firefly and IRSA application contexts, such as the _selection_ of a field of view, the arcminute option is presented.    The same logic should apply consistently throughout the Firefly world, I think.    Specifically: when the value is between 1 and 59 arcmin, display it as arcmin (with the ' symbol) with two digits of precision, i.e, as 1.0' through 9.9' or 10' through 59'. But if there is existing practice for something slightly different elsewhere in Firefly, it would be reasonable to re-use existing behavior.    Derives from IRSA-1606 and IRSA-1628.    Aimed at the May 2018 release.
Answer: 2700.0

User story: "memman looks like it returns handle=0 when locking 0 size files, and the resulting error causes worker to crash. The empty files are a result of loading problems and should not exist. Those chunks with issues are being added to the empty chunk list.    The bigger question is should this situation crash the worker and what is the appropriate course of action. Are empty files a legitimate possibility?         xrootd.log  {code:java}  [2018-03-26T22:56:45.305+0200] [LWP:278] ERROR wsched.ChunkTasksQueue (core/modules/wsched/ChunkTasksQueue.cc:410) - _memMgr->lock file system error QI=483131:24487;  [2018-03-26T22:56:45.305+0200] [LWP:282] ERROR wsched.ChunkTasksQueue (core/modules/wsched/ChunkTasksQueue.cc:410) - _memMgr->lock file system error QI=483131:24487;  terminate called recursively  terminate called recursively{code}  ls of offending chunk  {code:java}  [qserv@ccqserv117 log]$ ls -lh /qserv/data/mysql/LSST30/Source_35330*   -rw-rw-r-- 1 qserv qserv 5.9K Dec 13 21:58 /qserv/data/mysql/LSST30/Source_35330.frm  -rw-rw-r-- 1 qserv qserv 0 Dec 13 21:58 /qserv/data/mysql/LSST30/Source_35330.MYD  -rw-rw-r-- 1 qserv qserv 1.0K Dec 13 21:58 /qserv/data/mysql/LSST30/Source_35330.MYI{code}"
Answer: 188663.0

User story: "Convert ap_association to new LSST DM documentation formats, including clearing up numpydoc style docstrings."
Answer: 18517.0

User story: "ipyAladin because EPO uses it, RISE for writing my JupyterCon presentation."
Answer: 1479.0

User story: "Write a technote or other appropriate documentation for the prototype alert distribution system built in DM-13913."
Answer: 120832.0

User story: "String together a service which reads event files from disk, sends them to a Kafka queue, reads them into a “mini broker” filter, and delivers them to a consumer."
Answer: 109343.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 construction of sparse matrices in scipy is noticeably slow and currently causes the largest slowdown in performance for the new deblender (scarlet). We have optimized most of the code so that sparse matrices aren't needed, with the exception of the translation operators and PSF convolution operator. Since all of the sparse matrices we are using are essentially of the same form, banded diagonal matrices that can be thought of a single image window projected onto the morphology, we should develop a class that performs this simple operation for us. This is the last large boost we can expect in performance for the deblender and will give us a reasonable idea of the runtime of the algorithm.         This will require some refactoring of the data structures in scarlet, namely to keep the morphology as an image as opposed to a flattened vector, which was only done to allow us to use linear operators."
Answer: 11529.0

User story: "Create python classes for multiband exposures, images, and heavy footprints. These would essentially be python wrappers that take in a list of exposures (for example) and create a data cube with views to it that are slices in multiple dimensions. This would simplify the interface to multiband data and prevent developers from duplicating code."
Answer: 163072.0

User story: "The compiler check in {{lsst.sconsUtils.state._configureCommon}} fires whenever you {{import lsst.sconsUtils}}, even if you don't have any C++ code and all you want out of {{lsst.sconsUtils}} is some utility completely unrelated to C++. Besides just wasting time, this makes it difficult to run ci_hsc on a cluster nodes that don't have the latest {{gcc}} installed (as many don't, including the LSST Verification Cluster and New Tiger). The compiler check should only fire if we need it."
Answer: 7083.0

User story: "Ask for something from a dialog, open a notebook prepopulated with that information."
Answer: 20550.0

User story: Per [Slack discussion of 2018-03-27|https://lsstc.slack.com/archives/C2JP6PQLC/p1522192751000139], LDM-503 table 1 does not correspond closely to LDM-148, especially post RFC-456 (assuming that is adopted in close-to-current form, which seems overwhelming likely). Please refresh it, and turn all those "TBDs" into real document handles.
Answer: 172625.0

User story: "This is currently the repo scanner, the prepuller components that use the repo scanner, and whatever client libraries we find convenient (e.g. a bokeh display widget wrapper method).  It's much more convenient for them to be an installable library than to have to scatter them around various Docker build directories."
Answer: 34288.0

User story: "An oversight our build script for ndarray can cause it to prefer a non-EUPS Eigen installed in a system include directory over a EUPS-provided Eigen."
Answer: 76.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: {code:python}  [2018-03-27T13:48:00.428581Z]     @unittest.skipIf(noConnection, noConnectionStr)  [2018-03-27T13:48:00.428604Z]     def testStrip(self):  [2018-03-27T13:48:00.428627Z]         """Test config.strip  [2018-03-27T13:48:00.428648Z]             """  [2018-03-27T13:48:00.428672Z]         for strip in ("S", "N", "Auto", "Both"):  [2018-03-27T13:48:00.428695Z]             config = SelectSdssImagesTask.ConfigClass()  [2018-03-27T13:48:00.428719Z]             config.database = Database  [2018-03-27T13:48:00.428742Z]             config.strip = strip  [2018-03-27T13:48:00.428765Z]             task = SelectSdssImagesTask(config=config)  [2018-03-27T13:48:00.428787Z]             coordList = getCoordList(333.746, -0.63606, 334.522, -0.41341)  [2018-03-27T13:48:00.428812Z]             dataId = {"filter": "g", "patch": "20,5"}  [2018-03-27T13:48:00.428834Z]             runArgDict = task._runArgDictFromDataId(dataId)  [2018-03-27T13:48:00.428857Z] >           expInfoList = task.run(coordList=coordList, **runArgDict).exposureInfoList  [2018-03-27T13:48:00.428870Z]   [2018-03-27T13:48:00.428906Z] tests/test_selectSdssImages.py:167:   [2018-03-27T13:48:00.428952Z] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _   [2018-03-27T13:48:00.428988Z] ../../stack/DarwinX86/pipe_base/14.0-6-ge2c9487+36/python/lsst/pipe/base/timer.py:150: in wrapper  [2018-03-27T13:48:00.429013Z]     res = func(self, *args, **keyArgs)  [2018-03-27T13:48:00.429067Z] python/lsst/obs/sdss/selectSdssImages.py:299: in run  [2018-03-27T13:48:00.429090Z]     regionRaRange = _computeRaRange(coordList)  [2018-03-27T13:48:00.429126Z] python/lsst/obs/sdss/selectSdssImages.py:462: in _computeRaRange  [2018-03-27T13:48:00.429150Z]     raList = [coord.toIcrs().getLongitude() for coord in coordList]  [2018-03-27T13:48:00.429196Z] _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _   [2018-03-27T13:48:00.429209Z]   [2018-03-27T13:48:00.429253Z] .0 = <tuple_iterator object at 0x149805278>  [2018-03-27T13:48:00.429266Z]   [2018-03-27T13:48:00.429290Z] >   raList = [coord.toIcrs().getLongitude() for coord in coordList]  [2018-03-27T13:48:00.429314Z] E   AttributeError: 'lsst.afw.geom.spherePoint.spherePoint.SpherePoint' object has no attribute 'toIcrs'  {code}  
Answer: 437.0

User story: "psfex includes headers in the {{src}} directory, and they get installed under the same. However, Docker builds strip the {{src}} directory, meaning that the headers are removed. The headers should be put in the {{include}} directory to be immune from the stripping."
Answer: 9764.0

User story: "Document the notional development workflow in the JupyterLab environment."
Answer: 64004.0

User story: Per DM Leadership Team Face-to-Face Meeting, 2018-03-08/09: "Update LDM-135 to remove/clarify the misleading reference to users running code 'on their own hardware'"
Answer: 19217.0

User story: "Implement:  * {{Execution}}  * {{Run}}  * {{Quantum}}  and their associated {{Registry}} functionality."
Answer: 4373.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: "Run {{matchedVisitMetrics.py}} {{validateDrp.py}} and {{reportPerformance.py}}  with the HSC RC2 w_2018_12 outputs from DM-13795.  "
Answer: 2923.0

User story: "Run   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    with the w_2018_12 RC2 outputs from DM-13795"
Answer: 1735.0

User story: "Add errors in the photometry and the PSF - CModel measurements. Also include the seeing in each band."
Answer: 101217.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_14. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 23090.0

User story: "Evaluate the plan for porting HSC documentation to LSST."
Answer: 37262.0

User story: "Decide whether we want to spend more resources on CModel, or do something new."
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: [~<USER> reports the following error, which is fallout from DM-13741:  {code}  $ constructSky.py $ROOT --calib $CALIBROOT --rerun $RERUN --cores 1 --batch-type=smp --time 0.5  --job jobname--mpiexec="-prepend-rank" --id visit=6294^6296^6298    sky.detection INFO: Detected 1129 positive peaks in 963 footprints and 10 negative peaks in 10 footprints to 5 sigma  sky.detection INFO: Resubtracting the background after object detection  AttributeError on hda-mds02:32335 in reduce: 'BackgroundList' object has no attribute 'getImageF'  Traceback (most recent call last):    File "/ana/products.6.1/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0-hsc/python/lsst/ctrl/pool/pool.py", line 113, in wrapper      return func(*args, **kwargs)    File "/ana/products.6.1/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0-hsc/python/lsst/ctrl/pool/pool.py", line 239, in wrapper      return func(*args, **kwargs)    File "/ana/products.6.1/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0-hsc/python/lsst/ctrl/pool/pool.py", line 715, in reduce      *args, **kwargs)    File "/ana/products.6.1/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0-hsc/python/lsst/ctrl/pool/pool.py", line 572, in _reduceQueue      resultList = [func(self._getCache(context, i), data, *args, **kwargs) for i, data in queue]    File "/ana/products.6.1/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0-hsc/python/lsst/ctrl/pool/pool.py", line 572, in <listcomp>      resultList = [func(self._getCache(context, i), data, *args, **kwargs) for i, data in queue]    File "/ana/products.6.1/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_drivers/6.1-hsc/python/lsst/pipe/drivers/constructCalibs.py", line 1208, in measureBackground      exposure = self.processSingleBackground(dataRef)    File "/ana/products.6.1/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_drivers/6.1-hsc/python/lsst/pipe/drivers/constructCalibs.py", line 1238, in processSingleBackground      image += footprints.background.getImageF()  AttributeError: 'BackgroundList' object has no attribute 'getImageF'  application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0  {code}
Answer: 26.0

User story: "Review LDM-542 (Science Platform Design) and provide documentation engineering feedback for RFC-467."
Answer: 7.0

User story: "Implement RFC-462.    Also update meas_mosaic to optionally depend on obs_subaru."
Answer: 5647.0

User story: "In the spirit of disentangling computations from visualizations in the interactive QA framework of {{qa_explorer}}, write a task to compute columns of all quantities desired for {{pipe_analysis}}-style plots.  This should use the new object table parquet files ({{deepCoadd_obj}} dataset) generated by {{writeObjectTable.py}} to do computations on whole tracts of data at a time.  "
Answer: 59205.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: DM-13770 implemented butler-enabled reading/writing of Parquet tables via a {{FitsCatalogStorage}} shim.  However, in order to take advantage of the column-store nature, it is really necessary to define a new storage type that will enable extraction of specified columns without loading in the whole table.  [~<USER> suggests that this "basically boils down to grepping for all the places e.g. {{FitsStorage}} appears in obs_base and daf_persistence, and adding new clauses to various if blocks for the new storage type."  Additionally, a model for adding extra keywords to be passed to the loading function can be found with {{FitsStorage}}, which allows, e.g. {{butler.get("calexp_sub", dataId=..., bbox=...)}}.
Answer: 57813.0

User story: "l1dbproto should be more or less usable now for actual AP prototyping work. Integration issues related to that will be covered in this ticket."
Answer: 151231.0

User story: "In order to use {{testdata_jointcal}} with code that requires full transmission curves (such as {{fgcmcal}}), transmission curves need to be installed into the repo.  Currently, these are defined only for HSC, and the installation is described here: https://community.lsst.org/t/transmissioncurves-for-hsc/2632 .  This ticket is simply to install the HSC transmission curves into the HSC repo in {{testdata_jointcal}}."
Answer: 330.0

User story: "Write about how we use real-time chat, the transition from HipChat to Slack, and advantages of Slack."
Answer: 11523.0

User story: "Code clean up - remove xml xstream and old serialization     Remove old, unused code.   * At one point during the the conversion we had 3 serialization techniques.    * We no longer use the XML based xstream code."
Answer: 11860.0

User story: "Implement an initial basic (non-composite) version of:    * {{Registry.find}}  * {{Registry.associate}}  * {{Registry.disassociate}}  * {{Butler.get}}."
Answer: 1344.0

User story: "Contribute content to DM’s process paper for SPIE 2018. Repo is https://github.com/lsst-dm/spie-2018-dm-practices    Expected content includes:    - DM documentation (what we document)  - Documentation engineering (systems for creating and publishing documentation)  - community.lsst.org"
Answer: 30079.0

User story: "A list of things we can do to optimize server memory usage.   * evict image objects from memory based on idle time.   * evict old temp tables based on max count   * set a limit on the number of search results stored in memory   * report more table usage information in our status page   * analyze/improve DataGroup memory usage.   * IRSA-999: hierarchical directory structure for its temp files"
Answer: 31861.0

User story: "Presently L1db configures itself from INI-style file using Python \{\{ConfigParser}}. For better integration with pipeline tools {{pex.config}} should be used instead."
Answer: 1476.0

User story: "Apply final polish and submit."
Answer: 59487.0

User story: "Determine the equations for the collimated beam projector coordinate conversion object"
Answer: 43039.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: "Current L1DB implementation assumes HTM-20 indexing for DiaObject/DiaSource tables. There is code in L1db class that depends on that when doing region-based selection. It would be better to make this more flexible and client-controlled so that other indexing models could be tested/employed."
Answer: 151.0

User story: "sqrbot has been disabled for excessive login attempts.    Working with GH support to determine where it's spamming so we can fix it."
Answer: 7345.0

User story: "A system install ruby env is no longer needed as all builds are supposed to be run inside of a container."
Answer: 433127.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 information about the ITSC provided by [~<USER> to the DM Developer Guide."
Answer: 1394.0

User story: "The {{testdata_jointcal}} package has test data that should be suitable to test the basic functionality and running of {{fgcmcal}}.  Some tests in FGCM are long overdue."
Answer: 9923.0

User story: "Profiling {{measureCoaddSources.py}} reveals that about 1/3 of the time is going to AST transforms, which is much larger than desirable. For example, 15% of the time is spent in {{malloc}}, which is used by {{GetMapping}}, which is called by the {{ast::Mapping::apply*}} family of functions; and {{ast::Mapping::_tran}} (32.9%) calls through to something called {{ValidateMapping.part.59}} which uses a whopping 12.8%. The result is that when getting the PSF, we are spending more time in {{lsst::afw::geom::linearizeTransform}} than we are in warping the pixels to the coadd frame.    We need to determine whether our use of AST is inefficient or AST is inherently inefficient. Either way, we need to devise a strategy to deal with this."
Answer: 4948.0

User story: "Ongoing ticket for bugfixes to the environment.  Some of the things we have set up that allow JL to run happily turn out not to migrate well between installations."
Answer: 103520.0

User story: Contribute to the  "development model" section of the SPIE 2018 paper, as discussed on {{#dm-spie-2018-process}}.
Answer: 2874.0

User story: "Implement an interface to the {{DatasetStorage}} in the default schema that can be used by {{Registry}} and {{Datastore}}."
Answer: 1118.0

User story: "In order for composite dataset work to begin on the {{Datastore}} we need to have some things in place in {{Registry}} and {{Butler}}. Namely:    * {{Registry.addDataset}}  * {{Registry.attachComponent}}  * {{Registry.setAssembler}}  * {{Butler.put}}  * {{Butler.getDirect}} (i.e. we don't need {{Registry.find}} just yet)    This ticket captures that work (stealing some work from other tickets where needed, will adjust SP)."
Answer: 1430.0

User story: "Apply final polish and submit."
Answer: 73903.0

User story: "qserv-configure.py will not be used no more to configure this 2 services."
Answer: 24531.0

User story: "The DCR correction code needs to know the range of wavelengths permitted through a filter, not just the effective wavelength of the full band. I will add additional properties to `Filter` and define those properties for `obs_lsstSim` and `obs_decam`. Other packages should continue working as normal without being modified."
Answer: 29033.0

User story: "The [lsst-dm/milestones|https://github.com/lsst-dm/milestones] system was created to enable automatic generation of LDM-564 from a single PMCS export. Apply it to LDM-503 as well."
Answer: 4211.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: "For SPIE in June I need to write up a paper for the accepted presentation. The paper has to be submitted to the publication board by mid April. The abstract is:  {quote}  The Large Synoptic Survey Telescope is an 8.4m optical survey telescope being constructed on Cerro Pachon in Chile. The data management system being developed must be able to process the nightly alert data, 20,000 expected transient alerts per minute, in near real time, and construct annual data releases at the petabyte scale. The development team consists of more than 70 people working in six different sites across the US developing an integrated set of software to meet the LSST requirements. In this paper we discuss our agile software development methodology and our API and developer decision making process. We also discuss the software tools that we use for continuous integration and deployment.  {quote}"
Answer: 145359.0

User story: "1 graf on sqrbot, 2 on Jupyterlab"
Answer: 7175.0

User story: "Start poking around at the LDF cluster and see what we need to change, if anything."
Answer: 109195.0

User story: "ScienceSourceSelectorTask is slowly appending to a table when it can simply do the selection.  The loop at https://github.com/lsst/meas_algorithms/blob/f7dca96402cda034104c615be7ef821ab3aa9ea9/python/lsst/meas/algorithms/sourceSelector.py#L451 is unnecessary."
Answer: 6815.0

User story: "Christine has done work towards making Bokeh work in JupyterLab.  Adopt and adapt that."
Answer: 128.0

User story: "Implementation ticket for RFC-461.    Remove {{python/lsst/utils/multithreading/}} and the associated unittests, {{test_sharedData.py}} and {{test_lockProtection.py}}. "
Answer: 13454.0

User story: "The {{DataUnit}} descriptions in the schema {{YAML}} file are currently kept in the {{Schema}} object. This is undesirable because this is intimately coupled to {{sqlalchemy}} whereas {{SuperTask}} could be independent of it. So factor this out into a separate object. Should also be used for validating {{DatasetType}}, {{DataUnit}} (instances) and {{DatasetRef}} (by extension)."
Answer: 107727.0

User story: "Create a top-level script that will allow users to run both usage.py and usageplot.py with one command call; modify the README file to reflect these changes.  Also, modify how the calculation of elapsed times are done so that it is calculated with slurm data and not the calculated histogram data. "
Answer: 28942.0

User story: "Modify the node-hour and elapsed time calculations done by usage.py so that it will only print out two decimal places and will get the data directly from the SLURM data instead of the histogram data."
Answer: 37487.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 launched today at PCWG telecon a data Challenge on the determination of atmospheric transparency.    The details are in the talks at :    https://confluence.slac.stanford.edu/display/LSSTDESC/PCWG+Meeting+Page     March 15th         The trigger for this challenge is the acknowledgment that T_atmo is difficult to constrain from spectrometry or photometry alone. We wish to explore how to combine informations from both observations.          "
Answer: 142589.0

User story: Change usage.py so that the user can configure which slurm job names correspond to which code (ie, allow the user to specify that all jobs starting with "p1-mo", "p2-mo", "p5-mo" correspond to jobs that were run with mosaic.py instead of the accepted job names being hard-coded). Push the modified code to github. 
Answer: 31955.0

User story: "Modify usage.py/usageplot.py to output information about the overall execution times of given classes of tasks, e.g., how much time it took to complete all coadds, mosaics, and so on.  Push modified codes to github."
Answer: 18944.0

User story: "Following discussions on how composites work we have decided to move assembly/disassembly up a level to Butler.put/get and will change the API of datastore.put/get. URIs will no longer be returned and a separate method will be provided on datastore for creating URIs. Files being stored must now be associated with a datasetref explicitly in datastore registry."
Answer: 21788.0

User story: "At the present time, the HSC processing includes a new flat-field every run (approximately fortnightly).  Due to instability in the lamps, this creates large-scale sudden variations in the throughput on too rapid a timescale for the FGCM solution to handle (better calibration can be achieved with as few flat-fields as possible ... but that's a separate discussion).  It is possible to remove the large-scale features of the flat-field by measuring the flat-to-flat variation and incorporating this into the solution (or de-correcting the input stars).    At first I plan to test if the solution does improve on the RC dataset with the large-scale flat-field variations removed, and if so, then will incorporate these numbers into the final zeropoints."
Answer: 60967.0

User story: "Conversations at the JTM made me realize I should be using a proper SourceSelector to select sources in FGCM.  This includes comparing the speed of the current ad-hoc column based approach with the SourceSelector tasks.  "
Answer: 6190.0

User story: "Now that we have two different soft symmetry algorithms that perform nearly the same, we can test how adjusting the strength (`sigma`) of the constraints affects the results.    This ticket will include writing code to test the different symmetry algorithms and different `sigma` values, and run both codes with several different `sigma`s from 0 (no symmetry) to 1 (perfect symmetry) on ~100 blends. This should give us a rough idea about the runtime of the two algorithms, which is better (on average), and an optimal `sigma` value."
Answer: 8557.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: "Test the shape optimization algorithm by:  * Running the unit tests built during the coding of the algorithm  * Optimizing against a known elliptical Gaussian of differing S/N"
Answer: 375576.0

User story: "It has been reported that synpipe is broken by the latest changes to WCS. Fix all breakages such that synpipe can be run normally."
Answer: 71425.0

User story: "Plan out how best to implement the c++ classes which correspond to equations in [DM-13406|https://jira.lsstcorp.org/browse/DM-13406]"
Answer: 27.0

User story: "Implement the functions f(Q) and their derivatives as outlined in [DM-13406|https://jira.lsstcorp.org/browse/DM-13406]"
Answer: 71835.0

User story: "Using the work done in [DM-13404|https://jira.lsstcorp.org/browse/DM-13404] Create a c++ class that:  * Represents the prior as determined  * Contains methods to calculate derivatives  * Contains methods that translate between coordinate systems, and psf sizes"
Answer: 395815.0

User story: Run {{matchedVisitMetrics.py}} and {{validateDrp.py}} with the HSC RC2 w_2018_10 outputs from DM-13647.    Follow [~<USER>'s example:  {code:java}# Need to specify tract, otherwise one will get a meas_base failure.  matchedVisitMetrics.py "${REPO}" --output "${OUTREPO}" --config useJointCal=True --id visit=${VISITIDS} tract=${TRACT}    # Capture the output  validateDrp.py "${OUTREPO}"/matchedVisit_${FILTER}.json --noplot > ${OUTREPO}/metrics.log  {code}    Use the ticket branch of DM-13742.
Answer: 1192.0

User story: "Jointcal's current astrometry model fixes one visit to be the identity, to break the sensor/visit model degeneracy. This leaves one visit unable to correct for focal plane/sky distortions. We should instead fix one sensor, fitting the rest of the sensors to that one.    This may mean making one sensor's transform be the identity, or it may mean taking canonical values for one sensor but not letting them vary during the fit.    Because I'm digging into the astrometry code now, I'm going to try to do this as part of DM-13272."
Answer: 7568.0

User story: "For simple tests it's useful to run prototype against local sqlite file. There is some code in prototype that cares about engine type, need to extend it to understand sqlite."
Answer: 10035.0

User story: "As of merging DM-13727 to master the skypix package is no longer used by DM code. Please retire the package and then mark RFC-458 as implemented"
Answer: 32093.0

User story: "Remove the HiPS grid icon from the toolbar.  Then when a HiPS is added always add the HiPS grid layer with the checkbox turned off so that it is hidden by default.  This way a user has access to it without it being on the toolbar.    Add support for calling the IRSA hipslist.    this involves:     - app.config & app.prop     - uniq creator_did     - if title is blank use creator_did, last parts     - irsa.hips.method and irsa.hips.url         See also:    [https://caltech-ipac.atlassian.net/browse/IRSA-1556#add-comment]"
Answer: 11838.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: "Working on DM-13781 I tried to convert baseline schem to YAML and noticed some minor issues in that schema file:  * in some comments it uses {{</desc>}} instead of {{</descr>}}  * DiaSource index has a name IDX_DiaObject_htmId20   * DiaSource index IDX_DiaSource_filterName refers to non-existing field name    Also I need to verify that type of {{flags}} field in DiaForcedSource is correct (TINYINT)"
Answer: 130.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_12. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 18935.0

User story: "Make qa_explorer eups-installable."
Answer: 558631.0

User story: "Based on discussions with [~<USER> and [~<USER>, produce an outline design for the collimated beam projector coordinate transformation tool and circulate it to stakeholders for comment."
Answer: 63390.0

User story: "Running {{clang-tidy}} {{readability-implicit-bool-cast}} on {{src/detection/Footprint.cc}} revealed that the wrong overload of {{SchemaMapper::addMapping}} is called when given a string literal as the second argument.    We expect it to call {{Key<T> addMapping(Key<T> const& inputKey, std::string const& outputName, bool doReplace = true);}}, but instead it calls {{Key<T> addMapping(Key<T> const& inputKey, bool doReplace = false);}} because it prefers to cast to {{bool}} rather than create a {{std::string}} temporary.    I propose we add an overload taking {{char const*}}, make it primary and redirect the {{std::string const&}} overload to it.  Another alternative would be to find where it is called with a string literal and change it to a {{std::string}}."
Answer: 110809.0

User story: "Using the SLURM JobIDs detailed here ([https://confluence.lsstcorp.org/display/DM/S17B+HSC+PDR1+reprocessing),] create a color-coded node-usage plot, like those created with DM-13699, and also find the total node-hours of the entire run. Put the plot here, as well as in the confluence page above."
Answer: 1689.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: Hi [~<USER>,     It seems it is not possible to upgrade Qserv db schema to v2.  Indeed, migration with is not correct:  {code}  cat /qserv/stack/stack/miniconda3-4.3.21-10a4fa6/Linux64/qserv/12.1-138-g156793ae/share/qserv/schema/wdb/migrate-1-to-2.sql  --  -- Migration script from version 1 to version 2 of the qservw_worker database:  --  --  -  grant extended privileges to user 'qsmaster' for the database tables  --    GRANT ALL ON qservw_worker.* TO '{{MYSQLD_USER_QSERV}}'@'localhost';  {code}    `MYSQLD_USER_QSERV` should be replaced with `qsmaster`    Here the error log  {code}  qserv@ccqserv126:~$ qserv-smig.py -m -c mysql://root:changeme@127.0.0.1:13306/qservw_worker wdb  Current schema version: 1  Latest schema version: 2  Known migrations:    0 -> 1 : migrate-0-to-1.sql    1 -> 2 : migrate-1-to-2.sql (X)  ERROR 1133 (28000) at line 7: Can't find any matching row in the user table  Traceback (most recent call last):    File "/qserv/stack/stack/miniconda3-4.3.21-10a4fa6/Linux64/qserv/12.1-139-gc1b9a313+1/bin/qserv-smig.py", line 230, in <module>      sys.exit(main())    File "/qserv/stack/stack/miniconda3-4.3.21-10a4fa6/Linux64/qserv/12.1-139-gc1b9a313+1/bin/qserv-smig.py", line 219, in main      final = mgr.migrate(args.final, args.do_migrate)    File "/qserv/stack/stack/miniconda3-4.3.21-10a4fa6/Linux64/qserv/12.1-139-gc1b9a313+1/lib/python/lsst/qserv/wdb/schema_migration.py", line 176, in migrate      utils.loadSqlScript(self.engine, path)    File "/qserv/stack/stack/miniconda3-4.3.21-10a4fa6/Linux64/db/14.0+15/python/lsst/db/utils.py", line 443, in loadSqlScript      subprocess.check_call(cmd, stdin=script)    File "/qserv/stack/python/miniconda3-4.3.21/lib/python3.6/subprocess.py", line 291, in check_call      raise CalledProcessError(retcode, cmd)  subprocess.CalledProcessError: Command '['mysql', '--defaults-file=/tmp/tmpz0gef6oc']' returned non-zero exit status 1.  {code}    It works if the file is edited:    {code}  qserv@ccqserv126:~$ vi /qserv/stack/stack/miniconda3-4.3.21-10a4fa6/Linux64/qserv/12.1-139-gc1b9a313+1/share/qserv/schema/wdb/migrate-1-to-2.sql  --  -- Migration script from version 1 to version 2 of the qservw_worker database:  --  --  -  grant extended privileges to user 'qsmaster' for the database tables  --    GRANT ALL ON qservw_worker.* TO 'qsmaster'@'localhost';  {code}    A short-term solution (1st step) would be to add migration scripts to k8s configmaps (i.e. duplicated configuration files) and add a parameter in `qserv-smig` to change path to them.  An other solution (2nd step) would be to store `{{MYSQLD_USER_QSERV}}` as a parameter in   k8s configmaps, then create the migration script from its template and then use it in `qserv-smig`.    Please keep in mind that all files in qserv/admin/templates will be replaced with k8s confimaps, more flexible and editable at runtime.    [~<USER>, Could we please discuss this together in order to define an elegant design to this  configuration management?    Regards 
Answer: 4709.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 had a brief discussion at JTM/AH in Pasadena with AP team about re-using my L1DB prototype for their testing. One of the issues mentioned was that AP strongly prefers afw.table format for all kinds of DIA object, it would help them a lot if L1DB API worked with afw.table data instead of current data types (namedtuple).    I need to learn about afw.table and try to make L1DB API work efficiently with that data format."
Answer: 10901.0

User story: "Currently, {{pipe_analysis}} scripts have an optional {{writeParquetOnly}} flag to skip making plots and only write the parquet tables.  It might be desirable to factor that functionality out into a separate task.  One thing that might be interesting to test as part of this work would be what the performance is like if catalogs are just written at the patch level instead of consolidating all requested patches to a single full-tract catalog."
Answer: 70620.0

User story: "Prepare slides describing LSST's astrometric calibration and measurements for the Project Science Team / Science Collaboration Chair series talk on March 27."
Answer: 33056.0

User story: "Create a talk on the current status of DM documentation:    # Current status of project documentation  # Status of pipelines.lsst.io and Numpydoc/package documentation."
Answer: 31.0

User story: "The purpose of this talk is to orient DM staff (new and experienced) on the platforms that DM uses for online communications and best practices around their use."
Answer: 8.0

User story: "As per this request from [~<USER>:  {quote}We need to understand how much HSC data is processed   regularly, is that enough/too much, etc., and where to go from where we  are now. Please can you send half a page to a page summary of your   DRP-driven recommendations within a few days?{quote}   "
Answer: 114.0

User story: "Run   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    with the w_2018_10 RC2 outputs from DM-13647"
Answer: 5310.0

User story: Running the visit-level scripts using the current master of {{pipe_analysis}} ({{6b5727d}})  with the {{w_2018_10}} stack gave errors in getting the {{wcs}} dataset.       {noformat}  Traceback (most recent call last):    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/14.0-6-ge2c9487+51/python/lsst/pipe/base/cmdLineTask.py", line 408, in __call__      result = task.run(dataRef, **kwargs)    File "/home/<USER>stack/pipe_analysis/python/lsst/pipe/analysis/visitAnalysis.py", line 215, in run      raise RuntimeError("No datasets found for datasetType = {:s}".format(repoInfo.dataset))  RuntimeError: No datasets found for datasetType = wcs  {noformat}      It needs updates for the dataset name changes of DM-11138.   
Answer: 25456.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: "One of the drawbacks to using scarlet (the new deblender) is that it is difficult to adjust the strength of the symmetry constraint (as a proximal operator). Because symmetry is just a linear operator that calculates the difference between each pixel and it's symmetric partner, it is possible to move the symmetry constraint into the likelihood.         This has the added benefit of allowing the deblender to use the accelerated proximal gradient method (APGM), which is known to have faster convergence. So part of this ticket is also implementing the APGM in scarlet."
Answer: 15486.0

User story: "We discovered that {{pexConfig}} objects create {{__doc__}} (docstring) attributes automatically based on information passed to configuration constructors. This means that configuration fields are documented in the attributes of configuration classes inside the regular API documentation.    This is great, but can also fail if the automatically-generated config field docstring is not reStructuredText/Numpydoc compatible.    This ticket is to change the {{__doc__}} generators of {{pexConfig}} fields so that they output Numpydoc/reStructuredText docstrings."
Answer: 7549.0

User story: "Do the following:    - removed the GWT code  - remove GWT annotation  - remove unused methods that where used on the client  - Move constants around there were in GWT code"
Answer: 10008.0

User story: "Turn on building of sphinx documentation. We already use numpydoc for docstrings but some may need tidying as a result of the documentation actually being built."
Answer: 4085.0

User story: "Based on the result of discussions in DM-13751, work on the basic version of services needed to collect and deliver monitoring information."
Answer: 605425.0

User story: "Have discussions (with [~<USER>) and plan design for features needed at web service level for workers and out of replication framework to get the information we need out of them for a Qserv devops level dashboard."
Answer: 605448.0

User story: "Current implementation is apparently super slow, and looking at what it's doing (constructing a new dictionary of all fields via {{extract}} just to get one element from it, for every field), I can see why.    That could be cleaned up in Python but a lot of it is more naturally and definitely more efficient in C+++,+ and doing that will give us a C++ {{operator<<}}, too, which is nice."
Answer: 8507.0

User story: "Error handling for the new antlr4 parser – specifically for conditions where tree-navigation does not have an error but the query is not sufficiently populated.         Hook up a disable able (ifdef?) code that allows the antlr4 caught exception's message to be returned to the user."
Answer: 60351.0

User story: "Create a secondary index builder for the new ingest master/worker services"
Answer: 410598.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: "h4. Aerosol Optical Depth    AOD from Oct. 1st to 20th, 3hour steps.    The AOD above CTIO varies between 0.01 and .10 from within a few hours time scale.    The Cordillera is a north-south axis of lower AOD with respect to the ocean on the west, and Argentina on the East.    the movie is here :    https://confluence.lsstcorp.org/display/DM/Merra-2+Movies+October+2017"
Answer: 151413.0

User story: "{{DynamicDetectionTask}} tweaks the source detection level using the measured width in the distribution of PSF fluxes measured in empty sky. However, that distribution may not be centered on zero, which will also affect the source detection level. We should offer users the option of tweaking the background level."
Answer: 11527.0

User story: "In RFC-121 we adopted a policy of protecting master. This ticket is to add that documentation to the developer guide and include the settings needed to ensure that the pull requests are up to date with the base branch (which is our policy)."
Answer: 1187.0

User story: "Python 3 buffers {{sys.stderr}}, which means error messages can hang around in the buffer until the process completes (or, if it dies, those messages will never be seen). We need to ensure that we flush the buffers after running each element."
Answer: 38360.0

User story: "[~<USER> has identified additional HSC defects that should be masked. He writes:  {quote}  In this updates, I have added a mask to ccd=76 as well as ccd=33 and  43, as we found some affected area by bad pixels especially in NB0387.  Also I removed an unnecessary mask in ccd=43 which was mistakenly  placed for early period (before 2016-04).    The top-left corner of ccd=33 and 43 look quite bright on dark images  in some periods, but we determiend the areas to be masked on CORR  images both for typical broad-band (mostly HSC-G), and the worst  affected NB0387.  {quote}"
Answer: 366.0

User story: "See if an off-the-shelf WebDAV container can be procured and run in the PDAC"
Answer: 401506.0

User story: "We think we aren't actually using this, and we'd kind of like to use {{lsst.geom}} to mean something else."
Answer: 9895.0

User story: "Change fonts, tweak colors, and sizes in the https://github.com/lsst-sqre/lsst-sphinx-bootstrap-theme"
Answer: 101459.0

User story: "I just noticed that the tutorials haven't been updated for the change described here:    [https://community.lsst.org/t/transmissioncurves-for-hsc/2632]    Hopefully this will be an example of how it's easy to transfer content from c.l.o. to more formal documentation :)."
Answer: 51386.0

User story: "If kube-dns goes into a crash loop, it can occur because of a firewall issue.  Put an example of how to fix this."
Answer: 13.0

User story: "On some installations, ip forwarding has to be explicitly set.  Adding that to the documentation."
Answer: 11.0

User story: "We are getting warnings from Slack about rate limits on our ghslacker app.  Also the cache does not appear to be working."
Answer: 30369.0