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: "Set up a testing environment combining Qserv + the Replication system in the upper part of the IN2P3 cluster. This included the following nodes:  * *ccqserv125*: Qserv _czar_ and the Replication System's _controller_  * *ccqserv126* - *ccqserv149*: Qserv _worker_ servers and the Replication System's _worker agents_    Configure Qserv to use a separate set of ports and to use a separate data directories to avoid direct conflicts with the main stream (other) Qserv installation.    Preload the cluster with 1/6th of the following catalogs which are (as of now) being deployed at the NCSA's PDAC Qserv Cluster:  * *sdss_stripe82_01*  * *wise_00*    The data will be copied from the first 5 _worker_ nodes of that (source) cluster:  * *lsst-qserv-db01* - *lsst-qserv-db05*    The total amount of data to be transgferred from those 5 nodes is: *3.7 TB*    Extra actions to be taken in a context of this ticket will also include:  * building and deploying a specially configured version of the Qserv Docker container (to allow separate ports)  * packaging tools of the Replication systems into a separate container to be deployed at teh new cluster  * develop simple set of the management tools for starting/stopping the Replication System's services    Port number modifications in container image *qserv/qserv:tickets_DM-10424*:  {code:bash}  % cat admin/templates/installation/qserv-meta.conf    # Port number for worker management service  port = 25012    # Port number for cmsd server (not used in mono setup)  cmsd_manager_port = 22131    # Port number for xrootd server  xrootd_port = 21094    # Port number for mysql-proxy, this is the primary interface for qserv clients  port = 24040    # Port number for mysql server  port = 23306  {code}    Data directories for the Qserv instance:  {code}  /qserv/replication/  /qserv/replication/data/  /qserv/replication/log/  /qserv/replication/tmp/  {code}"
Answer: 8882.0

User story: After every outer outlier rejection loop, we should check the number of reference and measured sources per ccd, and issue a warning if they get too small (where "small" is defined by a config parameter).
Answer: 16014.0

User story: "A significant fraction of sources in HSC-R tract 9813 patch 3,4 have failed initial cModel fits (2.3% nan flux/objective, 10.2% negative flux), while 5.1% of dev/exp fits have nan flux/objective. After learning how to use the butler to display in ds9, I found that these failures come from a combination of sources near the edge of a patch, in/near the halos/diffraction spikes of bright stars, or from difficult/failed deblends, in roughly that order. I did not find any surprising failures - all of the failures also set a seemingly sensible failure flag.    The attached plot can be generated by the notebook created in DM-14118 (lsst-dev:/home/<USER>src/mine/taranu_lsst/cModelConfigs.ipynb)."
Answer: 101880.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: "I measured more diagnostics for differences in cModel performance with 2 vs 3 (default) vs 6 components in the initial fit. Performance-wise in HSC-deep r-band coadds, 2 components takes 6% less time than 3, while 6 takes 60% longer. Some galaxies have large differences in the quality of the initial fit, with slightly better fits on average with more components. However, the differences in the final fits are very modest, so there is little justification for using 6 components, and 2 might even be fine.    A large number of relevant plots/tables can be generated by the notebook created in DM-14118 (lsst-dev:/home/<USER>src/mine/taranu_lsst/cModelConfigs.ipynb)."
Answer: 66430.0

User story: "The Healpix utility HealpixIndex.js now only support down to level 13. Make is support all the way to level 20.   * Evaluate if it is possible in JavaScript   * If possible and can be done quickly implement the changes   * Change any other code limiting the depth.         _After evaluation:_    JavaScript can to integers of up to 56 bits.    The limit is because JavaScript cast numbers to a 32 bit signed int for bitwise operations (and, or, left shift, and right shift).  To make it go deeper we need to make function work with all 56 available bits.     Implemented:   * make HealpixIndex support down to level 25   * HealpixIndex can now use all 53 bits   * HipsUtil caching cleanup and optimization   * significant cleanup of HealpixIndex   * zoom in goes down to level 25   * Hips pixel level mouse readout   * A little more cleanup of ServCommand.java    _to test:_    load a hips, turn on the grid and zoom in really deep. Notice the hips pixel level readout"
Answer: 27170.0

User story: Change the "JupyterHub" page title to something more like "LSST Science Platform Interactive Environment"
Answer: 18636.0

User story: "Discourse now has native support for Lets Encrypt. https://meta.discourse.org/t/setting-up-lets-encrypt/40709?u=<USER>   Lets try it out."
Answer: 277928.0

User story: "Run matchedVisitMetrics.py validateDrp.py and reportPerformance.py with the HSC RC2 w_2018_15 outputs from DM-14123.  "
Answer: 18.0

User story: "Implement {{Registry.ensureRun}} which conditionally adds a given {{Run}}. If the {{Run}} already exists it should check that it is identical and silently ignore if it is or fail if not. If the {{Run}} does not exist it should add it."
Answer: 2661.0

User story: "Run   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    with the w_2018_15 RC2 outputs from DM-14123    Use the tickets/DM-13154 branch "
Answer: 1447.0

User story: "Convert {{lsst.afw.geom}}'s Python to Numpydoc, following the guidelines on [community|https://community.lsst.org/t/2760]."
Answer: 7378.0

User story: "Enables Sphinx support by uncommenting `automodapi` and fixing the errors and warnings."
Answer: 11358.0

User story: "Add Sphinx support to meas_astrom package."
Answer: 384634.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: "Recent change to admin/tools/docker/1_build-image.sh seems to have broken automated Qserv container builds"
Answer: 16.0

User story: "update 7.10.3    SUIT will not be ready for test of LDM-503-05, interface to the broker. "
Answer: 142297.0

User story: "Remove chart code supporting unused pre-multitrace architecture and server-side expressions.  Update the documentation for showChart parameters."
Answer: 80520.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_15. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}.     (Starting this week, the reprocessing actually has RC2 only, and no longer include the two WIDE tracts of RC1.)"
Answer: 2934.0

User story: "After a client uploads documentation to LTD’s S3 bucket, they must do a {{PATCH /builds/<id>}} call to tell the API that the build is complete. When this happens, the LTD Keeper app determines if the new build corresponds to an edition. If so, it copies the build over to become the new edition in the S3 bucket. For large sites, this takes a significant amount of time since actual data is being copied in the S3 bucket. The result is that the PATCH call routinely times out and produces a 503 server error.    The solution is to make this post processes asynchronous with the client API handling. Being a Flask app, we already have experience using Celery in Kubernetes to implement asynchronous tasks.    The goal of this ticket is:    # Add celery to LTD Keeper and its Kubernetes deployment  # Refactor the edition update into a Celery task."
Answer: 23226.0

User story: "The FGCM solution constrains the atmosphere parameters.  Currently, these are persisted in a table.  I will add the ability to output an atmosphere transmission function for each visit processed with FGCM.  Tests have shown that this can be done at sufficient accuracy (much smaller than 1 mmag offsets) using the FGCM pre-computed atmosphere tables without requiring a run of MODTRAN."
Answer: 48375.0

User story: "The abrupt relief of the Hawaii Island prevent the direct 2-D interpolation of Satellite data.    An understanding of the 3-D variability of the atmospheric parameters is needed :    I shall analyze 3-D data (inst3_3d_asm_Np (M2I3NPASM): Assimilated Meteorological Fields in https://gmao.gsfc.nasa.gov/pubs/docs/Bosilovich785.pdf) from MERRA-2.         Useful reading on 3-D model with abrupt orography :    [https://arxiv.org/pdf/1804.05200.pdf]     "
Answer: 95362.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: Ikeda-san has reported that the background tweak being applied in the {{DynamicDetectionTask}} is excessive when there are bright stars in the field.    On investigation, found that sky objects _are_ correctly avoiding the {{DETECTED}} areas, but the {{DETECTED}} area isn't anywhere as large as it seems just by looking at the image because the extended emission from the star is being purposely suppressed by the code (so the deblender isn't overwhelmed; this is the "wide temporary background" feature).    Suitable results can be obtained by doing an explicit background subtraction (using the {{base_LocalBackground}} measurement algorithm).
Answer: 1664.0

User story: "This notebook is to summarize the effects of changing the number of Gaussians in the initial fitting in the cModel task.    This includes running through the Jupyter workflow on lsst-dev, using the data butler, remembering how to process/plot data with Python and forgetting about R.    The notebook is currently at lsst-dev:/home/<USER>src/mine/cModelConfigs.ipynb and I will likely add it to a sensibly-named repository on lsst-dm."
Answer: 70685.0

User story: Rerun multiBandDriver.py with w_2018_14 on tract=9813 patch=3,4, varying cModel parameters like:    config.measureCoaddSources.measurement.plugins["modelfit_CModel"].initial.nComponents=2    This is to test whether changing the number of initial components can reduce the total running time without reducing the quality of the final cModel fit.    This includes going over slurm, lsst-dev file paths and miscellaneous pipeline info with Yusra.    An example command is:    multiBandDriver.py /datasets/hsc/repo --calib /datasets/hsc/repo/CALIB/ --rerun RC/w_2018_14/DM-13890:private/<USER>cmodelconfigs/w_2018_14_gradthresh_1e-3 --id tract=9813 patch=3,4 filter=HSC-G^HSC-R^HSC-I^HSC-Z^HSC-Y^NB0921 --configfile /project/<USER>cmodelconfigs/w_2018_14_gradthresh_1e-3/logs/config.py --batch-type=slurm --mpiexec='-bind-to socket' --job gthreshp1 --cores 6 --time 180000    where /project/<USER>cmodelconfigs/w_2018_14_gradthresh_1e-3/logs/config.py contains:    config.measureCoaddSources.measurement.plugins['modelfit_CModel'].initial.optimizer.gradientThreshold=0.001
Answer: 70736.0

User story: "Yusra showed me how to source the latest weekly build of the pipeline and running command-line tasks on HSC data on lsst-dev, e.g.:    source scl_source enable devtoolset-6; source /software/lsstsw/stack3/loadLSST.bash    setup lsst_distrib -t w_2018_14 # For that week    mkdir /project/<USER>cmodelconfigs/    multiBandDriver.py /datasets/hsc/repo --calib /datasets/hsc/repo/CALIB/ --rerun RC/w_2018_14/DM-13890:private/<USER>cmodelconfigs/w_2018_14 --id tract=9813 patch=3,4 filter=HSC-G^HSC-R^HSC-I^HSC-Z^HSC-Y^NB0921"
Answer: 64705.0

User story: "Add an interface which `obs_packages` can use to register cameras with the Gen3 Butler."
Answer: 2715.0

User story: "Divide usage.py into modules (putting like functions into the same module)."
Answer: 4669.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: "Reprocess the HSC RC dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], using Stack v15.0 and v14.0 (Wide-VVDS tract only). Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py(}}DM-10129/DM-11020). Use {{usage.py}} to compare these results."
Answer: 20354.0

User story: "Modify the README.rst file to refect new changes in the code, and modify usage.py so that key_len will be calculated from the input dictionary automatically."
Answer: 2960.0

User story: "Make a morphology only version of the star-galaxy classifier."
Answer: 26223.0

User story: "Using the results of testing the classifier on different depths (DM-13514) to finalise a version of the classifier that works well on all the test depths."
Answer: 26226.0

User story: "Add pyarrow to the shared stack, to support DM-13793, DM-13770, DM-13876, etc.  Also, if it doesn't break anything else, pandas 0.22 would be a good idea, too (improvements in parquet integration)."
Answer: 272208.0

User story: In SQuaSH, the drill down mechanism associates one or more metrics with a bokeh app. A bokeh app can have several plots, etc    For example, the drill down plots for AM1, AM2 metrics are implemented in the AMx bokeh app.    The mapping between metrics to bokeh apps should be done in a process called "application registration" . Other things may happen during that process like spinning up a bokeh server container for the new app, or adding the new app to and existing bokeh server container.    This process will make it easier for developers to add new bokeh apps to SQuaSH.    
Answer: 1305019.0

User story: "Modernize the packaging of https://github.com/lsst-sqre/ltd-conveyor in prep for the new CLI in DM-11638:    - {{setuptools_scm}} support  - Add a change log  - robust PyPI deploy from Travis  - pytest usage modernization  - Remove Python 2.7 support (remove future)  - Update Sphinx pipeline."
Answer: 24167.0

User story: "To facilitate cleaning up the StarSelector API, we want to remove the {{makePsfCandidates}} step from {{starSelector.run()}}, and turn it into its own Task. As far as we can tell, only one existing Task ({{pipe_tasks.measurePsf}}) uses that feature of StarSelector, so this should be easy to manage.    [~<USER> suggested a future RFC for merging this: we'll try a quick implementation first, and file a short RFC if it seems disruptive."
Answer: 30215.0

User story: "Estimate the node-hours spent in each kind of the five pipeline steps, in the S17B HSC PDR1 reprocessing. Add the results to the confluence page: [https://confluence.lsstcorp.org/display/DM/S17B+HSC+PDR1+reprocessing]   Make a pie chart similar to the one for the core-hours."
Answer: 85.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: "v1.1.0 currently cited in https://developer.lsst.io/git/git-lfs.html?highlight=lfs#installing-git-lfs is definitely too old. We have user reports of our Git LFS no longer working with older clients.  lsstsw is installing v2.3.4. [~<USER> things v1.5.5 might be ok. [~<USER> reports that 1.7 doesn’t work.    Pages to update:    - https://developer.lsst.io/git/git-lfs.html  - https://pipelines.lsst.io/install/git-lfs.html"
Answer: 16230.0

User story: "Translate the setup scripts to terraform config files for the OpenStack setup"
Answer: 18744.0

User story: "An outcome of the 2018 JTM hack day on documentation (https://community.lsst.org/t/package-documentation-hack-session-at-jtm-2018/2760?u=<USER> was the need for tooling to clean up documentation build artifacts. The current builds (for both single packages and multiple packages) leave behind multiple directories and need to be cleaned up to reset the build state.    This provides an opportunity to actually design a unified command line interface for building our stack documentation. In this ticket, I propose that we create two command line apps from the https://github.com/lsst-sqre/documenteer package.    One for the stack:    {code}  stack-docs build  stack-docs clean  {code}    And for single-package builds:    {code}  package-docs build  package-docs clean  {code}    There could even be use for other subcommands, like link check, lint, prepare release notes, and so on.    This command line app will be created with [Click|http://click.pocoo.org/6]."
Answer: 25176.0

User story: "Please add a readme file to {{datasets/sdss}}.  Content is described [here|https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance]."
Answer: 18935.0

User story: "Please add a readme file to {{datasets/lsstCam}}.  Content is described [here|https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance]."
Answer: 541348.0

User story: "Please add a readme file to {{datasets/ajltest}}.  Content is described [here|https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance]."
Answer: 5259.0

User story: "Please add a readme file to {{datasets/<USER>}.  Content is described [here|https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance]."
Answer: 1557.0

User story: "Please add a readme file to {{datasets/ctio0m9}}.  Content is described [here|https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance]."
Answer: 541351.0

User story: "Please add a readme file to {{datasets/comCam}}.  Content is described [here|https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance]."
Answer: 541352.0

User story: "Please add a readme file to {{datasets/auxTel}}.  Content is described [here|https://developer.lsst.io/services/datasets.html#responsibilities-on-ingest-or-maintenance]."
Answer: 541354.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: "{{ip_diffim}} currently produces many measurements that are not listed in the DPDD.  To populate the {{DIASource}} table we need to determine which columns in the output catalogs map to the {{cat}} schema."
Answer: 321298.0

User story: "Current alert_stream repo uses only a single template alert.  We want to change this to be able to send and receive sims data, for use in filtering and for the end-to-end prototype."
Answer: 1423.0

User story: "Should this package be migrated/marked as legacy?  "
Answer: 686349.0

User story: "Should this package be migrated/marked as legacy?"
Answer: 273363.0

User story: "Image qserv/qserv:dev image will be used for mariadb, so that depencies versions consistency will be ensured at build time."
Answer: 46800.0

User story: "Add the {{py:currentmodule}} directive to the python module documentation page template in the {{stack_package}} template."
Answer: 641.0

User story: "Symptom: Artifact candidates are being clipped when there not sufficient epochs remaining to do so.     Cause:  A crude N-Image is passed to filterArtifacts to compute the maximum number of epochs a candidate can appear in and be clipped. If there are < 3 epochs it's zero. (i.e nothing should be clipped). This N-Image is too crude.    The actual N-Image can be lower due to recorded chip defects (everything in the bad mask plane).    NOTE: This only affects coadds with small numbers of epochs"
Answer: 1705.0

User story: "Determine, on {{irsadev}} (which is why I can't do this now, because I'm offsite), whether the current Firefly HiPS code displays the http://amiga.iaa.es/hipslist maps in its index, and (whether or not they are in the index) whether it can display them."
Answer: 440486.0

User story: "Fix usage.py so that it will include data for failed jobs.   Add a special command-line option so that the user can specify which jobIDs have failed that they would still like to include in the data. "
Answer: 6938.0

User story: Modify usage.py so that it will output a dictionary containing the code names (singleFrameDriver, coadd, etc.) and their associated node-hours spent.  This will replace the "elapsed_times" output.
Answer: 1370.0

User story: "Per DM-14060, please install the new version of igprof on:    - All four lsst-dev stacks;  - Both Princeton Tiger stacks;  - Both Princeton Perseus stacks."
Answer: 1450.0

User story: "Entire images are being poisoned by a single NAN that came out of the forced measurement in dynamic detection. It needs to be robust against bad measurements."
Answer: 574.0

User story: "The gain, as measured by eotest's PTC task, should be ~the same as that measured by bfTask.estimateGains().    Runs some data through and see how they compare.    Ticket does not involve fixing differences found, simply reporting measured numbers for HSC chips.    Needs to be done after eotest's PTC task has been ported.    Present the results at SAWG meeting."
Answer: 279533.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  confluence page [https://confluence.lsstcorp.org/display/DM/Hawaii+Merra2+Data]    shows the PWV and AOD at Mauna Kea, Hawaii.    Regarding PWV, the most interesting point is its abnormally high level ~25mm, with respect to other telescopes' sites (~5mm @ CTIO, OHP). This may be due to interpolating measurements that are obtained from line of sight above the pacific ocean.    3-D correction methods to extrapolate from sea level measurements to the top of the mountain maybe mandatory."
Answer: 104174.0

User story: "igprof has a tendency to deadlock sometimes, but I recently put in [a pull request|https://github.com/igprof/igprof/pull/79] with a potential solution that works around the deadlocks. We're not sure how long it'll take to get to master and then formally released, so let's just pull the patches into our TaP package."
Answer: 1133.0

User story: We need to go back to a single checkbox to show the HiPS list.  Do the following:   * Make a single checkbox that is application configurable with a default of "IRSA Featured"   * The checkbox should be true.   * When checked do the featured query that will come from application configurable parameters.  The default should be ['IRSA']    * When uncheck do the full query that will come from application configurable parameters. The default should be['IRSA','CDS'] with the merge priority a parameter that is defaulted to ['IRSA']   * Update HipsListUril.resolveHiPSIvoURL to pass the default full query with the default server for it table search. It is necessary to make make HiPS IVO => URL resolution work
Answer: 8553.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: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_17. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}.   "
Answer: 30294.0

User story: "Add the ability to specify the resolution of usage.py on the command line."
Answer: 117.0

User story: "Create reStructuredText directives that build the module and package toctrees for pipelines.lsst.io.    Building these toctrees automatically will make the pipelines_lsst_io repo more robust to a changing composition of stack packages.    The list of modules and packages available for the documentation should generally be known from eups setups and the presence of manifest.yaml files.    The directives should allow for packages to be explicitly ignored even if they are automatically detected. This feature should be easy to implement and will provide a safety valve for automatic package detection.    The directives will be implemented in https://github.com/lsst-sqre/documenteer."
Answer: 2843.0

User story: "I've recently been trying to build and install things in a bash script, and I keep banging my head against {{setup: command not found}}, which is fixed by {{export -f setup}}. eups is trying to be POSIXly correct, so [it can't {{export -f}}|https://stackoverflow.com/a/29239838/834250], so we should export the function in {{loadLSST.bash}}."
Answer: 1456.0

User story: "Update {{lsst-dm/milestones}}, and flow the changes to LDM-503, LDM-564 and {{lsst-dm/images}}."
Answer: 1197.0

User story: "Run matchedVisitMetrics.py validateDrp.py and reportPerformance.py with the HSC RC2 w_2018_14 outputs from DM-13890.  "
Answer: 1.0

User story: "Run   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    with the w_2018_14 RC2 outputs from DM-13890"
Answer: 1078.0

User story: "In order to optimize the search of HiPS list and properties, create a method to cache the search result. The search result will be re-used repeatedly for any coming query and only be updated when the server have made any modification.           "
Answer: 2660.0

User story: "TablePanel was designed with built-in paging for larger data set.   However, it is now used for smaller data set where paging is not necessary.   Make paging optional.         This is to better support the use cases like showing FITS file header,  the option window for table display. Those display does not need paging options since data is usually small enough. Making paging optional gives us more flexibilities when using TablePanel for display."
Answer: 131064.0

User story: "In order to evaluate the atmospheric parameters as determined by the SNFactory standard stars' observations, I have downloaded NASA MERRA-2 data for Hawaii, starting with PWV and 03 for the years 2005-2017."
Answer: 10365.0

User story: "cloudmanager.py must use the openstack python client shade, instead of low-level python clients (nova, cinder, ...)"
Answer: 10039.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Currently the default behaviour for the tarball-matrix job is to have the "publish" option unticked". The majority of uses want to publish binaries when building them. Moreover on a small screen that option scrolls off the Blue Ocean popup bottom (with no obvious indicator) so it's easy to spend several hours building binaries and think it worked when it didn't really.           
Answer: 250290.0

User story: "Monitor the health of the puppet daemon on all the nodes in the LDF infrastructure to see how many changes they are making on each run, how long the runs are taking to apply changes, etc. "
Answer: 1.0

User story: "Refine thesholds on monitoring parameters to reduce false positives and catch missed events on systems that cause service issues."
Answer: 4.0

User story: "Understand options for tracking resource consumption of individual processes on batch compute system"
Answer: 2.0

User story: After DM-9584, the current bottleneck in the deblender is the translation and PSF operators, where (when PSF convolution is used) nearly all of the processing time is spent in a single function:      {code:python}  def apply_filter(X, weights, slices, inv_slices):      """Apply a filter to a 2D image X        Parameters      ----------      X: 2D numpy array          The image to apply the filter to      weights: 1D array          Weights corresponding to each slice in `slices`      slices: list of `slice` objects          Slices in the new `X` to store the filtered X      inv_slices: list of `slice` objects          Slices of `X` to apply each weight            Returns      -------      new_X: 2D numpy array          The result of applying the filter to `X`      """      result = np.zeros(X.shape, dtype=X.dtype)      for n, weight in enumerate(weights):          result[slices[n]] += weight * X[inv_slices[n]]      return result  {code}    Moving this to C++ and using the Eigen package is likely to improve the performance, and is the last tall pole remaining in optimizing the deblender. After this any performance increases will have to come from more clever implementations of certain algorithms and small optimizations throughout the code.
Answer: 15708.0

User story: "Refactor DataGroup   * DataGroup was written a long time ago as a table model to represent and manipulate tabular data.  Over the years is has gotten bulky and complicated.  Refactor it with emphasis on memory footprint and larger data set.    Table parsing   * Look into ways to improve table parsing, especially IPAC tables."
Answer: 135445.0

User story: "Investigate issue with DR backups failing to run due to blocking backups and transfer tasks. Design and implement provisional solution."
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: {code}  pprice@lsst-dev01:~ $ mergeCoaddDetections.py /scratch/<USER>madcash/DATA/rerun/20180305/IC1613 --calib /datasets/hsc/calib/20180117/ --output /scratch/pprice/test/ --id tract=0 filter=HSC-G^HSC-I^HSC-I2 patch=18,11  [...]  mergeCoaddDetections INFO: Read 1695 sources for filter HSC-G: DataId(initialdata={'tract': 0, 'filter': 'HSC-G', 'patch': '18,11'}, tag=set())  mergeCoaddDetections FATAL: Failed on dataIds=[DataId(initialdata={'tract': 0, 'filter': 'HSC-G', 'patch': '18,11'}, tag=set())]: OutOfRangeError:     File "include/lsst/afw/geom/SpanSetFunctorGetters.h", line 176, in void lsst::afw::geom::details::ImageNdGetter<T, N, C>::checkExtents(const lsst::afw::geom::Box2I&, int) const [with T = int; int N = 2; int C = 1]      SpanSet bounding box lands outside array {0}  lsst::pex::exceptions::OutOfRangeError: 'SpanSet bounding box lands outside array'    Traceback (most recent call last):    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/14.0-7-gc1eb65a/python/lsst/pipe/base/cmdLineTask.py", line 413, in __call__      result = task.run(dataRef, **kwargs)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_tasks/14.0-56-gcf273cdb+1/python/lsst/pipe/tasks/multiBand.py", line 476, in run      mergedCatalog = self.mergeCatalogs(catalogs, patchRefList[0])    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_tasks/14.0-56-gcf273cdb+1/python/lsst/pipe/tasks/multiBand.py", line 738, in mergeCatalogs      skySourceFootprints = self.getSkySourceFootprints(mergedList, skyInfo, skySeed)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_tasks/14.0-56-gcf273cdb+1/python/lsst/pipe/tasks/multiBand.py", line 804, in getSkySourceFootprints      s.getFootprint().spans.setMask(mask, detected)  lsst.pex.exceptions.wrappers.OutOfRangeError:     File "include/lsst/afw/geom/SpanSetFunctorGetters.h", line 176, in void lsst::afw::geom::details::ImageNdGetter<T, N, C>::checkExtents(const lsst::afw::geom::Box2I&, int) const [with T = int; int N = 2; int C = 1]      SpanSet bounding box lands outside array {0}  lsst::pex::exceptions::OutOfRangeError: 'SpanSet bounding box lands outside array'  {code}
Answer: 31.0

User story: "Study the current OpenStack cluster setup scripts to plan refactoring   * Use shade instead of nova,cinder and other low-level openstack python clients   * Remove deprecated bare metal commands"
Answer: 3920.0

User story: "Participate in the integration activity at NCSA. This covers time for Jim Parson, <USER> Htut-Khine Win, and designated manager(s)."
Answer: 11.0

User story: "Prepare L1 Integration system for Integration Activity. Make sure accounts, software, networking, etc. are set up to prepare for the on-site activity."
Answer: 14.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: "meas_mosaic includes an astrometric jacobian term in its photometric calibrations under certain circumstances. We need to determine when and how it should be applied, and allow the {{PhotoCalib}} object to incorporate that term (possibly as a contained SkyWcs or Transform-like object), and allow a user to apply it to an {{instFluxToMaggies}} calculation."
Answer: 188291.0

User story: At the top left corner of HiPS images, we display the HiPS name. Currently the property label is used for this. Since label is no longer in the HiPS standard v1, we should not rely on it. The decision process should be:   # user obs_title   # use label if obs_title not available. (only possible with older HiPS images since obs_title is required keyword)    Test case: HST-I image ([http://alasky.u-strasbg.fr/HST-hips/filter_I_hips/])    the obs_title is "HLA-I : F814W, F791W, F785LP and F775W", label is only "I"    We may need to have a limit in the title length here. (This is already in place currently, limited by the space available)         *Improvement on using the initial value hips_initial_fov:*  {quote}if ({{hips_initial_fov}} <1.0/3600) set the FOV to 180 degree;    else if ({{hips_initial_fov}} <9.0/3600) set the FOV to 9.0/3600 degree    else set the FOV to hips_initial_fov  {quote}  More details in  [https://jira.ipac.caltech.edu/browse/IRSA-1664]    *Improvement on using the initial values hips_initial_ra,* *hips_initial_dec:***  {quote}after user input a position at the image search panel, then clear it to empty, the HiPS display still uses it as the center position.    it should use the initial ra and dec if supplied by the HiPS image.   {quote}  *IVO Reference:*    Allow the API user to give a IVO reference to the HiPS data instead of a URL. Resolve it to a URL          
Answer: 8579.0

User story: After discussion among [~<USER>, [~<USER> and [~<USER>. Here is the list of changes to be made regarding HiPS image zoom and HEALPix grid level control:   # When user click "+" icon to zoom in on a HiPS image, we should try to do our best to honor the depth of order of the original HiPS. For example HST-NICMOS has order of 16, current Firefly stops zooming in at order level 13.    # Grid level: JavaScript integer support a large number. (Number.MAX_SAFE_INTEGER = 2^53^-1, or {{9,007,199,254,740,991}}). We should set the max grid level at 16 for now.    # According to HiPS standard, the grid is HEALPix Grid. We should name it as such in the layer control dialog.     Please reference IRSA tickets [https://jira.ipac.caltech.edu/browse/IRSA-1657,] [https://jira.ipac.caltech.edu/browse/IRSA-1658]  for more background explanation
Answer: 8621.0

User story: "Add a {{ConnectedSet}} helper (name optional) that allows for insertion of elements and connections and iteration over them in topologically sorted order."
Answer: 20240.0

User story: "The conda package versions should be updated as part of general house keeping at the start of each dev/release cycle."
Answer: 207572.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-12687 we moved the original stack package template to a `stack_package_legacy` directory of https://github.com/lsst/templates. But this still isn’t the right long-term home for that content because it isn’t a true _template_.    This ticket is to create a new repo in https://github.com/lsst-dm called {{pybind11_example}} that can house the content. The Developer Guide pages that reference this material will be updated to point there."
Answer: 9713.0

User story: "Create a {{ShimButler}} that emulates a minimal subset of gen2 {{Butler}} on top of gen3 {{Butler}}.  It should support all calls needed for coadd processing in {{ci_hsc}}."
Answer: 222949.0

User story: The goal is to address miscellaneous problems related to running DESDM packages under Python 3. This is a "bucket story" to capture the work of multiple staff members testing, debugging, and performing comparison runs.
Answer: 11423.0

User story: "This ticket is to enable the numpydoc conversion of ip_isr."
Answer: 18753.0

User story: "The monitor app tells a concise story: the impact of code changes on KPMs. My the attempt to expand it to display multiple metrics at once id not work. It does not scale well with the number of metrics (both re loading time and space in the screen). A dashboard-like interface with summary information for the KPMs is be better suited for that.    In this ticket I simplified the monitor implementation and put back the code changes feature."
Answer: 7511.0

User story: "Explicitly mention that {{lsst}} org membership and vetted dependencies are requirements for getting a package in {{lsst_distrib}}."
Answer: 1099215.0

User story: "While the basic {{get}} and {{put}} interface should be backwards-compatible, some things CmdLineTasks do are not currently planned to be implemented in Gen3 in a way that looks the same as Gen2:   * Slicing Datasets (i.e. retrieving subimages)   * Subsets and incomplete data IDs   * DataRefs    When possible, add (temporary) shims to daf_butler to make things work the same way.  When it's less messy to add special-case code to the CmdLineTasks themselves, do that instead (which should be rare).    This ticket will focus on the easiest steps of the pipeline included in ci_hsc: the CmdLineTasks defined in pipe/tasks/multiBand.py.  Those will be run against a Gen3 repo build by converting a Gen2 repo containing the outputs of all previous steps."
Answer: 282262.0

User story: "Make it possible to run a {{CmdLineTask}} against a Gen3 Butler repository via a options in {{pipe.base.ArgumentParser/CmdLineTask.parseAndRun.}}    Code may or may not be merged to master; if it does, it'll be via an *optional* dependency on daf_butler.    For now, we will expect all data IDs to be passed explicitly; there will be no expansion or wildcard support."
Answer: 31485.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: "Gen2 repositories already have SkyPix datasets (reference catalogs) that use possibly-different levels of HTM.  That'll be tricky to support with our (probably naive) plan to have a single SkyPix pixelization and level in each Registry.  Come up with a design that solves that problem, and at least think about whether HiPS/MOC datasets pose a similar problem (they probably do).    Options include:   * RFC rewriting reference catalogs to a common level.   * Have a common level for all join tables, but allow Datasets to use other levels (with either another join table or an in-database function to relate them).    We also need to think about how to deal with HTM vs. HEALPix; we need support for HTM for reference catalogs now (and already have the necessary low-level code in sphgeom), but we know we'll need to do HEALPix in the future.  That will probably require adding HEALPix to sphgeom (backed by third-party HEALPix libraries, but still not trivial), which we'd rather not do now (not part of this ticket).  But once HEALPix is available, do we do a big-bang switch to it and drop HTM, or do we design a system that permits both to exist within the same registry?    Outputs: write up a proposed design (Confluence or DMTN), and RFC it."
Answer: 775214.0

User story: "_Do the following:_   # Cubes: fixed the bugs related to moving between HiPS cubes and regular hips   # Cubes: display the correct current plane number and the total plane number  when switching between HiPS cube   # Cubes: honor the data_cube_* properties and show information about the 3rd dimension   ** Use: {{value = crval3 + (cubeIdx - crpix3 ) * cdelt3}}   # Make field of view and target optional and then, if they are not specified by the user, default to the HiPS properties {{hips_initial_ra}}, {{hips_initial_dec}}, and {{hips_initial_fov}}.  If neither are available show 180 degrees at 0,0."
Answer: 1530.0

User story: "Make up the characterization report for the v15 release.  This will be done on the master branch of https://github.com/lsst-dm/dmtr-62."
Answer: 10190.0

User story: "{{hammer5}} no longer exists    https://developer.lsst.io/team/drp.html#connecting-from-outside-princeton"
Answer: 92371.0

User story: "Add liveness and readiness check"
Answer: 8571.0

User story: "qserv-run-dir and qserv-configure will no more be used in k8s setup."
Answer: 34394.0

User story: "Update the Docker documentation for Pipelines v15 (essentially make the notes in https://github.com/lsst/pipelines_lsst_io/pull/74 the default, and then get rid of information on the old Docker configuration)."
Answer: 12556.0

User story: "jointcal's {{Gtransfo}} object (a mutable 2->2 transform designed for astrometry and optimized for being fit) should have a name that better matches our standards. I created {{PhotometryTransform}}, so I suppose an appropriate new name might be {{AstrometryTransform}}?"
Answer: 352695.0

User story: "This ticket is to draft a test specification in LDM-533 for the LDM-503-5 Alert Distribution milestone."
Answer: 357037.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: "After updating and changing the chart framework in PR [https://github.com/Caltech-IPAC/firefly/pull/568] the API and in particular the function call addXYplot used in Gator need to be updated. The chart now resulting in calling this function doesn't show the latest changes with single trace UI discussed in IRSA-1522.    IRSA/Gator html code shouldn't change. Instead, the exposed API should be updated to use the latest API underneath and return a similar chart object as the one displayed in other apps such as FinderChart and IRSAViewer/Time Series tool. "
Answer: 5311.0

User story: "As an author, provide feedback on the SPIE 2018 paper."
Answer: 56209.0

User story: "Take a look at how Jenkins works. Understand how jobs are scheduled. Think about how we could integrate a job which exercises the ap_verify system.    It would be great if this included integration with SQuaSH, but if it did nothing other than pass/fail that would also be fine in the short term.  "
Answer: 100847.0

User story: "It turns out that {{cp_pipe}} has an implicit dependence on {{eotest}}.  Please resolve the dependence by including it in the table file.  This may also involve moving it into either {{lsst-dm}} or {{lsst}}."
Answer: 242718.0

User story: "Implementation of RFC will require an approved LCR adding the relevant data products to the DPDD (LSE-163) and DMSR (LSE-61). (This will then trigger an LDM-151 update, but that's outside the scope of this ticket.)    [~<USER> (or delegate) will start this process by proposing wording for the DPDD and DMSR that will satisfy SUIT needs.    We'll run that by [~<USER> to sanity check in terms of the sizing model.    Then work with [~<USER> or [~<USER> to submit it to the CCB."
Answer: 207308.0

User story: "{{daf_butler}} is the first package to fully implement the RFC-45 strategy for managing license and copyright information. Despite this, GitHub is not detecting the GPL-3.0 license and displaying it through its API/UI. This means that something might be wrong with the RFC-45 strategy (ideally we want our licenses detected). This ticket will research why this is, and hopefully suggest a resolution."
Answer: 36377.0

User story: "Following DM-13910, it's now possible to disable the C++ compiler check in `scons`, allowing us to build pure-python packages without a conforming C++ compiler (e.g., running ci_hsc on cluster nodes). Activate this on the following packages:  * ci_hsc  * ci_ctio0m9  * pipe_drivers  * pipe_tasks"
Answer: 1350.0

User story: "Create a CLI for https://github.com/lsst/templates. This CLI should provide an interface for discovering templates, and then rendering templates. (We can’t reasonably use Cookiecutter alone because the Cookiecutter CLI doesn’t understand our single-file Jinja2 templates).    The CLI will be created with the [Click library|http://click.pocoo.org/]."
Answer: 13048.0

User story: "Foreign key support is disabled by default on Sqlite3. Enable it and see what breaks."
Answer: 209.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 presentation is available at:  * http://www.slac.stanford.edu/~<USER>TALKS/2018_Apr_LSST_GroupMeeting/QservReplicationSystem.pdf"
Answer: 20389.0

User story: "Run KPM30 tests on LSST30 data on the lower half of IN2P3."
Answer: 682931.0

User story: "I think the purpose for this ticket was to go through the integration select statement test queries and write unit tests that verify that the select statement generated by the antlr v2 parse is the same as the one generated by the antlr4 parse, and fix any issues that come up."
Answer: 88928.0

User story: "Discuss requirements for reformatted EFD schema with [~<USER>."
Answer: 37053.0

User story: "Once kubernetes environment is deployed on PDAC nodes (IHS-845), we need to setup the deployment of SUIT portal using k8s. "
Answer: 89333.0

User story: SuperTask pre-flight will accept user "filter expression" which limits processing of the data to a subset of the unit universe (in addition to the limit based on the existence of input datasets). The expression would be come a part of SQL WHERE clause but on user side it should looks as simple as possible, sort of  {noformat}  Tract = 5 and Patch IN (1,2,5,9) AND Visit BETWEEN 1002 AND 1099  {noformat}    We need a parser that can understand this sort of expressions and translate this into SQL (or any sort of Python construct) usable by registry.    Scope of this ticket would be selecting a library/tool for building filter parser and defining a baseline grammar for the expression.
Answer: 44520.0

User story: "Attend the IVOA meeting, give a presentation of Firefly new feature: HiPS image display.          session agenda: http://wiki.ivoa.net/twiki/bin/view/IVOA/InterOpMay2018Apps"
Answer: 89353.0

User story: "Attends the EPO all hands, participate in and contribute to the discussion of Science platform, Jupyter NB/lab, and visualization. "
Answer: 18259.0

User story: "Convert an LSST dataset to parquet format."
Answer: 47730.0

User story: This ticket applies to the usual Firefly image pixel coordinate readouts in the upper right of the display window, when the currently displayed image is a HiPS image map.    # Display as "pixel size" the "tile pixel angular size" from column 4 of the table in the screenshot linked to this ticket (which is also Figure 5, on page 11, of the HiPS standard), for the _currently displayed level_ ("order") of the selected HiPS map.  This display, therefore, should change as the zoom level is changed.  # By default, display galactic coordinates on the second line of the readout (instead of the usual default of image pixel coordinates).  # Remove the option to display the "image pixel" coordinates ("FITS Image Pixel" in the selection dialog) for HiPS image.  (See DM-13981 for a future ticket to restore this capability in an appropriate way.)
Answer: 5380.0

User story: "Finish porting pipe_tasks docs from doxygen to numpydocs following <USER>s hack day instructions."
Answer: 77777.0