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: "I wrote and ran some systematic tests in pyprofit to compare the accuracy and speed of galaxy profile integration and convolution using pyprofit/libprofit and GalSim. When evaluating the profile and convolving with an analytic PSF, GalSim is considerably faster for n<4 and more accurate in most cases, especially for small axis ratios. However, ProFit can be faster for large Sersic indices (n>4) and supports an essentially infinite range, whereas GalSim is limited to 0.3<n<6.2. Furthermore, the tests I ran used 3x oversampling in libprofit, which has further room for optimization - as does libprofit's profile integration scheme. Thus, it's worth keeping support for libprofit in the future.    pyprofit code: [https://github.com/lsst-dm/pyprofit]    pyprofit arguments to generate a table of benchmarks (in pycharm run configuration format, which is human-readable xml): https://github.com/lsst-dm/pyprofit/blob/master/.idea/runConfigurations/pyprofit_bench_integ_long.xml    benchmarking notebook: [https://github.com/lsst-dm/modelling_research/blob/master/jupyternotebooks/pyprofit_benchmarks_plot.ipynb]    The plots should render better in a browser now, but I attached some copies anyway."
Answer: 30065.0

User story: "The pyprofit ([https://github.com/lsst-dm/pyprofit)] code originally supported only the optimizers from scipy.optimize, using L-BFGS-B by default. I added support for using pagmo2 ([https://github.com/esa/pagmo2/|https://github.com/esa/pagmo2/)]), an optimization library with a wider array of optimizers and interfaces to other libraries, as well as both python and C++ interfaces. I tested a few examples and L-BFGS-B with numerical gradients seems to work better than derivative-free optimizers for N<20 parameters, but it remains to be seen how general that result is.    Pycharm run configurations for HSC tests are available here; this will be kept up to date (see also DM-14647):    [https://github.com/lsst-dm/pyprofit/blob/master/.idea/runConfigurations/pyprofit_fit_hsc.xml]    At the time of writing, the command to run the HSC example is    python3 $PROJECT_DIR$/examples/hsc.py    Galaxy cutout arguments:    -radec 134.67675665 0.19143266 -size 19.9asec    Arguments to test pagmo vs scipy optimize (enabling automatic gradients for pagmo):    -optlib pygmo -grad 1    -optlib scipy    The -algo <algorithm> flag can be set, but valid arguments depend on the optlib:    [https://esa.github.io/pagmo2/docs/python/algorithms/py_algorithms.html#pygmo.cmaes]    [https://docs.scipy.org/doc/scipy/reference/generated/scipy.optimize.minimize.html]"
Answer: 24346.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: "PyProFit ([https://github.com/ICRAR/pyprofit/|https://github.com/ICRAR/pyprofit/)]) is a python wrapper for our (Taranu, A. Robotham & R. Tobar) galaxy fitting library libprofit ([https://github.com/icrar/libprofit/|https://github.com/icrar/libprofit/)]) and its R interface ProFit ([https://github.com/ICRAR/ProFit/|https://github.com/ICRAR/ProFit/).]). I adapted some of the existing examples in pyprofit into a python interface for galaxy fitting, with most of the same features as ProFit. This is now a fork of pyprofit on lsst-dm: [https://github.com/lsst-dm/pyprofit]. I will use pyprofit for further exploratory work for new modelling methods/codes prior to integration in meas_modelfit."
Answer: 54831.0

User story: "I thought that it might be possible to determine analytic solutions for the convolution of exponential profiles with each other and with Gaussians, which ought to make them faster to compute and allow for exponential mixtures models. I determined that it's possible in 1D, but the 2D generalization is not quite right - the profile is slightly off and I couldn't get the normalization correct, plus it's not clear how this would generalize to non-aligned ellipses.    I attached the R scripts I wrote and plots showing the 1D and 2D solutions compared to ProFit convolutions (oversampled for accuracy)."
Answer: 40468.0

User story: "Asked to read through [https://dmtn-073.lsst.io/v/DM-12620/index.html] trying to make sure there isn't anything obvious missing before opening the review to larger group.    Work includes asking <USER>questions or providing feedback on Slack.    Meetings with the NCSA DB admins about the schema and sending their initial impressions/questions to Jim.     "
Answer: 40675.0

User story: "There are several components related to publishing an official science pipeline release:    * jenkins instance  * s3 bucket for eups tags/products  * s3 bucket for doxygen builds  * an Apache directory format indexed site to host the (s3 backed) {{EUPS_PKGROOT}}  * a site to access doxygen  * github org hosting git repos for eups products (uses github API)  * remote versiondb git repo (pure git remote -- not currently required to be github; must be writable)  * https accessible copy of {{newinstall.sh}}  * remote git repos for CI related build tools: eg., {{lsstsw}}, {{ci-scripts}}) (not required to be github; read-only)  * docker registry hosting images for build tools and science-pipeline base images (can be read-only)  * docker registry to which science-pipeline release images are published (must be writable)  * squash instance to publish {{validate_drp}} results to    To date, there has never been complete end-to-end testing of the release process external to the production environment.  DM-14138 added support to {{sqre-codekit}} to allow previously hard-coded urls to be overridden but further effort is needed to allow the jenkins jobs and jenkins instance configuration to support alternative environments. "
Answer: 35157.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Some tuning is required to use overlay2 on Centos7. It will be done on openstack testbench."
Answer: 250.0

User story: "This is to capture the work effort in testing the performance of FIrelfy image display in NB deployed at Kubernetes commons in NCSA.          The work and suggestions are here:    The performance study was prompted by demos of the qa_explorer notebook at the DMLT, with the ginga and the Firefly backends. Using the lsst-lspdev notebook environment and Firefly server, I checked the performance of Firefly panning at zoom level=1 on a 4k by 4k image. Panning to a new position typically took 5-10 seconds but occasionally as long as 20. There is a strong caching effect when panning to a position previously visited, as then the pan typically took between 0.2 and 1 second.    With assistance from Simon, I was able to install the qa_explorer notebook and operate its interactive feature of selecting a star or galaxy from a scatter plot, and zooming and panning to its location on the closest coadd image. The ginga backend typically took a few to 5 seconds to display the desired location. The Firefly backend typically took 15-20 seconds for the display, zoom and pan.    The Firefly display backend always shows the entire image fit to a frame, before zooming and panning to the desired location. Performance could be improved by batching together the initial display, zoom and pan. Alternatively, if DAX imageserv were available it would be more efficient to make a cutout at the desired location and then display it — a solution we used in our forced photometry demo on the PDAC.    The show_fits method of FireflyClient will take an initial zoom level as an argument. For the qa_explorer application, it would be better to set the initial zoom level to 1, to skip the time-consuming display of the entire image. Currently the afw.display abstraction doesn’t support this — it was developed for ds9 where zooming is easy. The mtv method of afw.display could be modified to take optional arguments like zoom level and a position on which to center the display.     "
Answer: 1.0

User story: "Per DM-14508, {{scikit-learn}} is to become a conda dep."
Answer: 126707.0

User story: "Provide general support for early use of the kubernetes cluster for May 2018. Covers small emergent tasks."
Answer: 40458.0

User story: "Configure firewall settings to allow desired and appropriate container-level access. This includes puppetizing configuration."
Answer: 14.0

User story: "Run benchmark for container-level security assessment (kube-bench). Adjust configuration based on recommendations, in conjunction with LDF security, system administration, and other technical staff."
Answer: 17.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Incorporating l1dbproto into ap_association requires definitions and mappings between afw schemas and db schemas. This ticket will expand the methods make_minimal_dia_*_schema to more closely approximate that of l1dproto and the DPDD. This will also create mappings between the ip_diffim schemas input into association and the DIA schemas."
Answer: 26258.0

User story: "The recent updates to the sourceSelectors in DM-9832 broke fgcmcal (which is not in lsst_distrib and not regularly tested yet).  This ticket will update fgcmcal."
Answer: 60.0

User story: "Run {{colorAnalysis.py}} script on all coadds from the S18 PDR1 outputs (DM-13666)."
Answer: 617174.0

User story: "Here is the striking slide from S. Dagoret presentation last week.    What is going on in the blue? This should be zero here, as there are no telluric features (?):((n)    [https://indico.in2p3.fr/event/17361/contributions/62542/attachments/48385/61105/2018-05-25-atmspectra-final.pdf]    !Capture d’écran 2018-05-31 à 09.51.51.png!"
Answer: 32245.0

User story: "Add man pages since we will have interactive users."
Answer: 101.0

User story: "See if we can get RISE running in Lab environment well enough to allow it to be used for JupyterCon presentation."
Answer: 131109.0

User story: "Work on presentation for JupyterCon talk"
Answer: 123880.0

User story: "Datashader API changed; figure out how we need to adapt our examples and re-adopt master branch."
Answer: 41502.0

User story: "Since ${HOME} at LSP isn't lsst-dev:${HOME}, we can just root the JL filebrowser in ${HOME} which is more what people expect."
Answer: 2952.0

User story: "Bucket for tracking down performance or functionality problems at LDF."
Answer: 134105.0

User story: "As we add more configurable parameters (e.g. horizontal component scaling) we need to extend our deployment tool to understand and exploit them."
Answer: 134107.0

User story: "As the upstream code base changes, so too must our deployment.  This tracks the ongoing set of fixes needed to stay compatible with the current code base."
Answer: 134109.0

User story: "Update the code that generates the gaussian mixture model, which is to be used as the prior in the regularized moments code, so that all of the parameters are measured in sky tangent plane coordinates. This ticket should also convert the code in the regularized moments algorithm that uses this code to also operate in sky tangent plane coordinates."
Answer: 13.0

User story: "man isn't installed."
Answer: 6.0

User story: "At LSP the provisioning doesn't actually copy /etc/skel so we need to do that as a pull from the user at startup time.    "
Answer: 28.0

User story: "Currently the regularized moments code is inside meas_modelfit. This ticket should move the code out into its own meas_ext package. The name of the algorithm is changing to informedShape."
Answer: 3011.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: "Multiband driver can run detection on a coadd, but this code path is rarely exercised. The method signature to detect coadd sources in pipe_tasks has changed, but was not updated in pipe_drivers. This ticket should fix the call to runDetection in detectCoaddSources"
Answer: 307.0

User story: "The code that synpipe uses to insert fake stars into an image rightfully throws an exception when it tries to generate a psf in the part of an image that has no data. This brings down a whole processing run with an un-handled  exception. Fix so that the exception is caught and handled so that it does not bring down the whole run."
Answer: 2896.0

User story: "The exposure time for warps is well-defined, but it's not being set."
Answer: 65299.0

User story: "Refactor TF setup for ease of use and edge cases"
Answer: 20188.0

User story: "It would be very helpful if the jupyter environment had a {{.user_setups}} file by default, with just a comment saying what the purpose of the file is."
Answer: 1295.0

User story: "Commit {{2d46b0cd620cc07b45baa191dcc280e9130dfeb9}} makes {{filter}} optional in the test {{Butler}} template for {{calexp}}. This is needed because {{fitler}} isn't handled properly.  Filter is a special case because both {{abstract_filter}} and {{physical_filter}} exist but {{filter}} does not."
Answer: 361149.0

User story: "Write simple script to compare each of the segments (HDU) for two FITS files (i.e. Truth FITS file vs new FITS file)"
Answer: 1.0

User story: "PDF export fails for complex notebooks.      Fixing it will require newer (non-Centos-packaged) pandoc and LaTex installations."
Answer: 352.0

User story: "Harvard team and CNRS-LAL team have been independently performing and reducing observations for telescope throughput calibration from airmass regression.    Here is the (quite satisfaying) result shown at the LSST/DESC Calibration Workshop (May 25th 2018):    [https://indico.in2p3.fr/event/17361/contributions/62542/attachments/48385/61105/2018-05-25-atmspectra-final.pdf]    !Capture d’écran 2018-05-28 à 16.55.55.png!"
Answer: 36141.0

User story: "Merge configmaps and init containers definitions in master and worker pods"
Answer: 23030.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> some initial thoughts for the nightly report tool.    From [LCR 1203|https://project.lsst.org/groups/ccb/node/2174] we can list the different LSST subsystems that require a nightly report functionality:    * Telescope & Site  * Camera   * DM  * Observatory Control System     and LCR 1203 emphasizes that they must utilize a common reporting infrastructure.    We can start looking at DES Night Summary tool: http://des-ops.fnal.gov:8080/nightsum    It is a static HTML page generated at the end of each night that consolidates information from different DES systems like the electronic logbook, the observatory and telescope control systems, infrared camera and the QC pipeline that runs on the mountain    From the DES experience you see how useful is to have a *single report* that combines information from different systems in a coherent narrative. It makes it easier to correlate information and avoids duplication of necessary information that would be required on different reports.     It is challenging, each LSST subsystem will have different systems underneath and a nightly report still needs to be an easy-to-read summary. Accessing four different pages already seems too much... right? conway's law here?    One aspect that facilitates (and perhaps should be a requirement for each system) is to provide a programatic API to access the data, otherwise it will be hard to collect and centralize the information in the nightly report.    For instance, for the DM part will report the KPMs computed by some QA SuperTask triggered after the prompt processing. The KPMs will be available trough a REST API like we have in SQuaSH  making it easy to access the information.    Thinking about SQuaRE's toolchain for the nightly report tool, a notebook could have the code necessary to collect all the information from the different systems APIs and also include the report narrative. This notebook would run automatically once all systems are done and the result would be published as a static page using the same infrastructure we have to publish our technotes.     It is also possible to have interactive plots in the static generated technotes using for instance the sphinx-bokeh extension as demonstrated in https://sqr-019.lsst.io/    "
Answer: 50171.0

User story: "Earlier this month there were discussions the pegasus workflow tests might be needed again. I tried to submit the two small tests on VC using a recent stack (w_2018_18), and realized a few things have changed from last year that would need fixes accordingly. Here I'm only applying quick config overrides to avoid the problems.  If we want to revive this, a more proper fix is to include the new data types. "
Answer: 5.0

User story: "Due to travel it was preferable to review DM-11953 without a unit test.  This ticket is to create the missing tests, possibly with advice from [~<USER>."
Answer: 216703.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: "To help get a stable photometric solution, we can try implementing a magnitude-space fitter.    We should do it by creating a new {{MagnitudeTransform}} class, and related Mapping, Model, and {{PhotometryFitter}}, that all will use the magnitude instead of flux, so we still have the flux-based model available.    This ticket is to implement and test the Simple model."
Answer: 87488.0

User story: "Modernize Documenteer's PyPI deployment by:   * switch to setuptools_scm (common standard)   * use conditionals for PyPI deployment so only one matrix job deploys to PyPI."
Answer: 207.0

User story: "DM-14520 neglected to actually add a butler.yaml config to the repo, which makes it impossible to actually run the conversion without doing that step manually."
Answer: 2386.0

User story: "Debug Qserv shared scan scheduling and related issues for KPM30."
Answer: 62025.0

User story: "Currently, the update_dia_objects method within AssociationTask performs separate loads for each DIAObject it updates. This ticket will change this to one access to the database for all DIASources that are associated with the updated DIAObjects."
Answer: 47625.0

User story: "The {{ap_verify}} dataset framework is currently documented in the Sphinx documentation for {{ap_verify}}. This documentation assumes that individual datasets will at least have documentation of their GitHub repository, so that the pages can be linked from lists of known datasets or from examples. However, no such documentation has been written yet.    This issue adds a documentation placeholder to {{ap_verify_dataset_template}}, and standardized package documentation to {{ap_verify_hits2015}}, {{ap_verify_testdata}}, and any other datasets existing at the time of work. It will *not* move the documentation of the dataset framework from its current location in {{ap_verify}}."
Answer: 38913.0

User story: "`stac` can make GraphViz files but `stack` is currently nit working - `run` command depends on a Butler and I need to update it to work with new repos. It would be useful to be able to generate GrpahViz plots from existing QGraph without executing stuff, will try to see how it can be done with the existing options."
Answer: 1436.0

User story: "Modify {{pipe_tasks.multiBand}} to detect, merge, and measure sources across multiple DCR subfilter coadds. The documentation will also need to be updated, and a new unit test should probably be added."
Answer: 14656.0

User story: "For some use cases, for instance, the HSC reprocessing on the LDF environment, we need an option in {{dispatch_verify.py}} to skip the upload of data blobs to SQuaSH.  "
Answer: 362.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2018_22. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 20325.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 pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp  # matchedVisitMetrics.py  # validateDrp.py   # reportPerformance.py     with the w_2018_20 RC2 outputs from DM-14339"
Answer: 8.0

User story: "Add test for composite calexp to Butler"
Answer: 10579.0

User story: "For {{ci_hsc}} it is required that {{Butler}} objects be pickleable. Fix this."
Answer: 13417.0

User story: "* Automatically register components, and  * Allow for duplicate insertion only if identical."
Answer: 14487.0

User story: "Separate the cluster provisioning (terraform) from k8s setup"
Answer: 3249.0

User story: "Observation: When images loaded, the tab for images become active.    Most cases we want the tab to become active when images load.  This does not always look correct when many images load slowly as in LSST testing environment.    This ticket is to record the observation and add more use cases later so we can discuss and decide if the behavior needs to change."
Answer: 273292.0

User story: "The classifier pickles need to be kept somewhere that the butler can find them and it needs to know about them. The resulting catalogue also needs to live somewhere butler accessible it could either overwrite the deepCoadd_obj files that [~<USER> makes (one I've double check it isn't doing anything silly) or it could go into a new data type but it would be mostly a duplicate of the deepCoadd_obj with a few extra columns added in another extension."
Answer: 216058.0

User story: "This is to record the effort of SUIT team supporting the NB access to Firefly server, QAs, and debugging.    The issues and bugs need to be addressed are recorded in different tickets. "
Answer: 14749.0

User story: "Please add the following utilities to Firefly docker container:    - procps (http://procps.sourceforge.net/)  - wget  - emacs    These utilities will be helpful when debugging a dockerized Firefly deployment using kubectl."
Answer: 14773.0

User story: "Geom was removed from the dependency tree in a previous ticket.  ci_hsc still expects in its test that setup packages are recorded, causing a failure."
Answer: 273.0

User story: "Add {{operator[](Box2I)}}, {{operator[](Point2I)}}, {{operator[](int, int)}} to C++ image interfaces, taking into account xy0.  Wrap for Python using a temporary alternate method name.    Remove old Python implementation of {{\_\_getitem\_\_}} and {{\_\_call\_\_}}.    Update any code that used the old APIs to use the new temporary ones.    Switch from temporary names to {{\_\_getitem\_\_}} and update downstream code accordingly (via regex or similar).  "
Answer: 68670.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: {noformat}  $ setup lsst_distrib -t w_2018_20  $ processCcd.py  /datasets/hsc/repo/ --output /scratch/whatever --id visit=34644 ccd=5  root INFO: Loading config overrride file '/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/obs_subaru/15.0-8-gde10c556+2/config/processCcd.py'  Traceback (most recent call last):    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_tasks/15.0-11-g8c8473f0/bin/processCcd.py", line 25, in <module>      ProcessCcdTask.parseAndRun()    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/15.0-6-gfa9b38f+1/python/lsst/pipe/base/cmdLineTask.py", line 570, in parseAndRun      parsedCmd = argumentParser.parse_args(config=config, args=args, log=log, override=cls.applyOverrides)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/15.0-6-gfa9b38f+1/python/lsst/pipe/base/argumentParser.py", line 569, in parse_args      self._applyInitialOverrides(namespace)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/15.0-6-gfa9b38f+1/python/lsst/pipe/base/argumentParser.py", line 754, in _applyInitialOverrides      namespace.config.load(filePath)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pex_config/15.0-1-gae1598d+9/python/lsst/pex/config/config.py", line 558, in load      self.loadFromStream(stream=code, root=root)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pex_config/15.0-1-gae1598d+9/python/lsst/pex/config/config.py", line 578, in loadFromStream      exec(stream, {}, local)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/obs_subaru/15.0-8-gde10c556+2/config/processCcd.py", line 23, in <module>      config.charImage.measurePsf.sourceSelector["objectSize"].sourceFluxField = 'base_PsfFlux_flux'    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pex_config/15.0-1-gae1598d+9/python/lsst/pex/config/configurableField.py", line 109, in __getattr__      return getattr(self._value, name)  AttributeError: 'MeasurePsfConfig' object has no attribute 'sourceSelector'  {noformat}    Is this due to DM-10797? 
Answer: 51.0

User story: "There are mentions of {{IcrsCoord}} in {{qa_explorer}}.  These need to be updated to the new coord objects."
Answer: 45813.0

User story: "Dataset's foreign keys to DataUnit have been commented-out in the schema file.    Uncomment them and get things working (actually, we'll need to update their representation in the schema in order to make them compound keys).    I've already started this in trying to get the schema on DM-12620 synced with master, and I think I'm pretty close, but it makes sense to split this off from that ticket."
Answer: 849.0

User story: "Assume 100 users, 100GB?? Per user, 3TB static"
Answer: 6914.0

User story: "Investigate Firefly scaling/balancing"
Answer: 6914.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "When upload a ds9 region file to be overlaid on an image, the keyword is required to be lower-case characters. Lets make it case insensitive .    test:   * do image search on firefly on target (0,0, j2000) and upload footprint file from 'Load DS9 Region File' popup.   * go to firefly/demo/ffapi-footprint-test.html, and add footprint layer from the footprint tool page."
Answer: 8479.0

User story: "Two suggestions (only!) for the footprint menu in Firefly:    # Make it hierarchical, so that, e.g., all the HST instrument footprints appear in a submenu.  (I would like to have at least three footprints for LSST, for instance.)  # Make its content part of the application configuration, e.g., controlled via the {{suit}} package for LSST or the {{ife}} package for IRSA.  The Firefly repo could still contain a standard set of footprint files, but more could be added in the application, and even some of the standard ones suppressed, perhaps?"
Answer: 180092.0

User story: The decam ConstrainedPhotometryModel is the smallest test case I have that exhibits "instabilities" (e.g., mac/linux differences, fitting failures due to chi2 increase during outlier rejection when turning off rank update or changing the flux error pedestal), suggesting that it has a substantial non-linear component. With the output of DM-14509, I can look at the properties of the matrix itself, probably using a jupyter notebook.    Depending on the size of the resulting matrix, I could also try the same with validation_data_hsc, which also exhibits such instabilities, but has a lot more components.
Answer: 151235.0

User story: "[~<USER> suggests that we should implement a [line search|https://en.wikipedia.org/wiki/Line_search] in jointcal, to deal with the non-linearities in the photometric model (and because we may eventually have those in astrometry, as the astrometry model gets more complex). He suggested using [Brent's method|https://en.wikipedia.org/wiki/Brent%27s_method], which is [available in GSL|https://www.gnu.org/software/gsl/doc/html/roots.html#c.gsl_root_fsolver_brent]. It might be easier to just take the code directly from GSL, instead of writing an interface layer, given the way the nature of the jointcal models.    At the top of the outlier rejection loop in {{FitterBase.minimize()}}, this would look something like:    {code}  Eigen::VectorXd delta = chol.solve(grad);  scale = lineSearch(delta);  offsetParams(delta*scale));  {code}  "
Answer: 66446.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 need to explore the properties of the matrix and gradient in jointcal's {{ConstrainedPhotometyModel}}, but the sparse matrix code in Eigen doesn't include many options for doing so. To better facilitate this, [~<USER> suggested outputting the matrix elements and creating a dense matrix from it. This ticket is just for the output and checking that it's sensible: detailed exploration will be in a different ticket.    A quick search suggests that one can pass the sparse matrix to one of Eigen's constructors to directly get the dense matrix. It might be easier to explore the matrix properties with numpy."
Answer: 16543.0

User story: "Make a stub package for scikit-learn"
Answer: 221793.0

User story: "[~<USER> found issues using ap_association with the way schema's are treated and mapped from ip_diffim to the prototype prompt products database. This ticket will remove the mapping from AssociationTask and put it fully within the placeholder database task AssociationDBSqlite."
Answer: 216.0

User story: "The following code gives segfault:  {noformat}  import lsst.afw.image as afwImage  from lsst.afw.table import SourceTable  from lsst.meas.algorithms import SourceDetectionTask  from lsst.meas.deblender import SourceDeblendTask    exposure = afwImage.ExposureF('/datasets/hsc/repo/rerun/RC/w_2018_18/DM-14243/01111/HSC-Z/corr/CORR-0017962-101.fits')    schema = SourceTable.makeMinimalSchema()  detectTask = SourceDetectionTask(schema=schema)    # these two lines need to switch the order  table = SourceTable.make(schema)  deblendTask = SourceDeblendTask(schema=schema)    detectResult = detectTask.run(table, exposure)  catalog = detectResult.sources  deblendTask.run(exposure, catalog)  {noformat}    This is because the schema is modified when SourceDeblendTask is constructed.  So the above code passes a catalog of a different schema to deblendTask than its schema.     Add a check to make the error clearer.     "
Answer: 4063.0

User story: "Remove usage of the daf_persistence Persistable framework and Boost.Serialization in all other packages, preparing them for us eventually dropping daf_persistence entirely when the Gen2->Gen3 transition is complete.         Also rewrite some formatters in daf_persistence to continue Gen2 Butler support for those objects until the Gen3 transition is complete.  (Plenty of Gen2 formatters already do not use daf.persistable.Persistable, so this should not be too hard)."
Answer: 222063.0

User story: "Implement full round-trip read and write from YAML for PropertySet and PropertyList.    Started here: https://github.com/lsst/daf_persistence/commit/6ed767db014fbcec7478ff7d616de3b0fc691b14"
Answer: 71165.0

User story: "Enable the login from SUIT portal, use the credential to determine if the user can have access to SUIT portal, pass the credential to DAX API to do searches, pass the credential to JupyterLab to authenticate the access to user file storage space."
Answer: 541383.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: "As of now, we have [25 “owners” of the lsst GitHub organization|https://github.com/orgs/lsst/people?utf8=✓&query=+role%3Aowner] (& [19 for lsst-dm|https://github.com/orgs/lsst-dm/people?utf8=✓&query=+role%3Aowner]).    Some of these people no longer have an LSST affiliation; many of them are no longer in positions that make it appropriate to administer GitHub on our behalf. Please prune this list to something manageable, and document the criteria for somebody to be listed as an owner."
Answer: 1257434.0

User story: "There is a incorrect reference to {{display_ds9}} in the sConstruct file in display ginga.  Change this to {{display_ginga}}."
Answer: 159.0

User story: "# Allow different projects, with different names, to use {{lsst-sphinx-bootstrap-theme}} (make the name templated)   # Fix LSST logo branding (don't use the inverted version)   # Further improve colours and typography.    This will allow the theme to be used with the nb.lsst.io site ( DM-14406)"
Answer: 10801.0

User story: """Stack"" means nothing."
Answer: 1115.0

User story: "See if we can get the qa_explorer plots (including the ginga display) working in the JupyterLab environment. "
Answer: 304230.0

User story: "As part of the ease-of-use improvements in DM-14391, we would like to ask that two environment variables be provided in Jupyterlab deployments.    FIREFLY_URL = path to the default Firefly server    e.g. [https://lsst-lspdev.ncsa.illinois.edu/firefly] for the [https://lsst-lspdev.ncsa.illinois.edu/nb] environment. A trailing slash will work.     FIREFLY_HTML = default landing page for Firefly, which is appended to the URL.    We'd like this set to 'slate.html' as we intend to build around this view."
Answer: 1171.0

User story: "Take the star galaxy classifier defined in DM-14110 and DM-14109 and turn it into a task. This will also involve learning how to use pandas."
Answer: 67331.0

User story: "User expression parser is almost complete, it can now be integrated in supertask CLI. "
Answer: 13213.0

User story: "DM-14149 made it possible to display HiPS images at level 20 level by using JavaScript 56 bit integer. It created new methods to do bit-shift.  This ticket to test the result from science point of view. "
Answer: 99601.0

User story: "Figure out the relationship between the various planes of interest involved in Fourier optics.  Namely,    * The pupil plane   * The focal plane   * The Fourier conjugate to the focal plane   * The sky   * The Fourier conjugate to the sky    Write it up.     "
Answer: 54427.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "When running {{ci_hsc}} in multi-process mode I encountered various race conditions in {{Registry}} access. While making {{Registry}} entirely safe under concurrency, while preserving its modularity, might be a stretch we should at least attempt to fix the most obvious showstoppers.    I intend to:  * Disable {{autocommit}} mode and use transactions exclusively.  * Open one connection per {{Registry}} instance (rather than one, or multiple, per method call) and use proper transaction nesting.  * Where possible, merge multiple steps and checks into a single SQL call.  * Attempt to get as close as possible to strong exception safety.    This ticket is a bit experimental, since much depends on the actual support within {{sqlalchemy}} but we should be able to:    1. Do better than we do currently.  2. Get a better understanding of the limitations.    Ideally all individual {{Registry}} method calls will be fully ACID, but combinations of method calls will probably not be."
Answer: 24294.0

User story: "From Wednesday May 23 - Friday May 25 there will be an LSST/DESC calibrations workshop in Paris: https://indico.in2p3.fr/event/17361/timetable/#all . The purpose of the workshop is to bring LSST and DESC people (and one Gaia person) together to discuss calibration plans for LSST and to ensure that the cosmology science needs will be met by the project.  I will be specifically presenting on FGCM and application to LSST; and issues with Gaia photometry that has been released to date. "
Answer: 22731.0

User story: "Python packages installed via {{pip install --user}} have their command line executables installed in {{~/.local/bin}}. Can we add that directory to the user's default {{PATH}}?"
Answer: 1349.0

User story: "JL doesn't have git-lfs installed, and it needs to."
Answer: 1400.0

User story: "Create Requirements Matrix for HeaderService in the form of a spreadsheet"
Answer: 2717.0

User story: "Idle culler is still not working."
Answer: 186.0

User story: "A {{Datastore.put}} should raise when the file already exists (perhaps adding an option to force it)."
Answer: 402525.0

User story: "The mini-broker isn't covered by design documentation in LDM-151 or (as far as I know) any other document. Write a design document for it."
Answer: 248095.0

User story: "While working on DM-14155, I discovered that Linux and Mac produce different results in the DECAM ConstrainedPhotometryModel tests. This may be a hint about why that model is unstable and not producing good fits, or it may be due to something else. Either way, I should understand what's going on, which is going to require a bunch of debug printing, and maybe looking at the matrix elements themselves.    As an example, after the error scales are frozen, the mac chi2/ndof is {{5073.41/2108}}, while on linux it is {{5072.94/2108}}. Subsequently, different outliers are rejected and the final fits are measureably different."
Answer: 1068613.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 would like multiple MOCs to be able to be displayed at once.   * Load more MOCs with the upload panel   * -Load MOCs with the search panel the can search the CDS server.- _Moved to DM-15570_         For immediate implementation, we will put a test button at the top."
Answer: 155254.0

User story: "Implement the visual display of MOC data in Firefly    Initially, display the HEALPixels actually identified in the MOC (which is just a list of HEALPixel IDs in NUNIQ format) as polygons overlaid on a sky display in Firefly. Include this in the usual Firefly layer control behavior.   * We would like multiple MOCs to be able to be displayed at once, with selectable colors used.   * It may be useful to enable the control of both polygon boundary colors, transparency, etc. _as well as polygon fill_ with adjustable transparency.   * Be able to switch between outline (wireframe) and transparent color fill   * MOC show as a HiPS layer with checkbox off, should lazy load with any HiPS         Implementation technical Notes:   * We should read the table using our normal fits table reading and put all the rows (only one column) into the store.   * Each number (NUNIQ) can be translated to a HealPix level and number and then to 4 WorldPt corners using functions in HipsUtil and HealpixIndex   * We need to make new DrawObject will need to be created that can draw a filled polygon, fill with a transparent color for overlaying. Possibly we could modify FootprintObj or MarkerFootprintObj.    * If the points reduce to a single point (based on zoom level) it should draw a single point.   * The drawing layer should be able to change the color in our standard way.     "
Answer: 123614.0

User story: "Finish implementing RFC-460; see that ticket for description."
Answer: 25843.0

User story: "In the absence of DM-13990, I'll use HTM at depth 7 for everything, because that's what the reference catalog in ci_hsc uses.    This will include updating daf_butler to work with the master version of skymap, which has slightly different APIs for sphgeom interoperability than the gen3-middleware branch."
Answer: 64430.0

User story: "Update the FitsExposureFormatter (and FileFormatter as needed) to provide efficient access to components and subimages without reading the full file."
Answer: 391872.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 {{Butler.put}} on concrete composite datasets, the Registry is informed of all component Datasets, but the Datastore is not (and PosixDatastore, at least, does not loop over them itself).    I think the right fix is to add a call to {{Datastore.ingest}} in {{Butler.put}} for each component.  That will cause {{PosixDatastore}} to look up the formatter for each component based on its StorageClass (which will generally not yield the right formatter, because it'll yield one appropriate for writing standalone objects of that type) and DatasetType (which could work, but only if we configure Formatters explicitly for every component of a composite DatasetType).  To fix that, I think we'll want want to also support Formatter lookup on strings that look like {{<StorageClass>.<component>}}."
Answer: 24.0

User story: "This is to start up the user documentation site for the notebook aspect of the LSST Science Platform. This site is akin [https://pipelines.lsst.io.|https://pipelines.lsst.io./]    The domain is [https://nb.lsst.io|https://nb.lsst.io,/] (this domain is expected to only be used for the early prototyping phase of the LSST Science Platform).    The repository is https://github.com/lsst-dm/nb_lsst_io."
Answer: 14344.0

User story: I have been tasked by LSST DESC with writing up requirements on Survey Geometry and Masking to communicate with LSST Data Management (DM) to ensure that we provide the  maps and/or tools that DESC needs to perform cosmological analyses.  The survey on survey geometry was intended to get at the question of "what does survey geometry mean to you?" This was open-ended enough to ensure that there is an opportunity to bring up issues that I have not considered.  In general, the survey geometry representation will define a set of quantities (e.g., sky brightness, seeing, number of images, etc) over certain spatial scales, combined with a veto mask (survey edges, very bright stars, CCD gaps before enough tiles have dithered over gaps).  Given this information, we can reconstruct not only where objects *are* in the survey but where they *aren't*.  This is essential for computing window functions, random points, incompleteness correction factors, etc.  
Answer: 1.0

User story: "Update LDM-503 with the test specification for LDM-503-1."
Answer: 40.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: "Improvements to {{firefly_client}} and {{display_firefly}} to allow initialization without specifying Firefly server or channel, in these two use cases:   # User in a Jupyterlabdemo environment which also has a Firefly server   # User running on own machine with dockerized Firefly server     * Rename the first parameter for initializing {{FireflyClient}} to be {{url}}, and remove the {{basedir}} parameter by folding it into {{url}}. An example of {{url}} is [https://lsst-demo.ncsa.illinois.edu/firefly].   * When {{firefly_client }} is imported, default {{url}} to the value of the environment variable {{FIREFLY_URL}} if it is defined. If it is not defined, default to [http://localhost:8080/firefly|http://localhost:8080/firefly.]. For the parameter {{html_file}}, default to the value of the environment variable {{FIREFLY_HTML}} if it is defined; if not defined, default to None which is equivalent to an empty string.   * By default, do not specify channel and allow it to be auto-generated. In {{display_firefly}}, expose the channel, the browser url, and the instance of {{FireflyClient}}   * In {{FireflyClient.launch_browser}}, check if the webbrowser open has failed, and display a message that the browser couldn't be auto-opened, directing the user to open the url in a browser window. In the Jupyter notebook, the message is a clickable link.  * Update documentation, and in the case of {{firefly_client}}, example notebooks.  * Reorganize {{display_firefly}} documentation for publication to pipelines.lsst.io."
Answer: 14610.0

User story: "Integrate Oracle cluster fully into existing LSST infrastructure once configuration is stable-- security, system management (puppet), etc."
Answer: 80897.0

User story: "Test system/database performance using a known astronomical pipeline framework."
Answer: 40408.0

User story: "Perform system-level configuration testing-- memory, storage, etc. Resolve issues,"
Answer: 70805.0

User story: "Run Oracle tests and benchmarking, e.g., SLOB. Resolve issues."
Answer: 40409.0

User story: "Our setup isn't working with current JupyterHub and a base_url set."
Answer: 6913.0

User story: "Idleculler fails if there is a base_url set."
Answer: 12.0

User story: "Prepare slides on HSC PSF wavefront model to deliver at weekly DRP meeting.     "
Answer: 1.0

User story: "Add gen3 conversion to the ci_hsc SCons build and test that we can use a Gen3 Butler to {{get}} Datasets {{put}} with a Gen2 Butler."
Answer: 12975.0

User story: "When testing the Gen3 ShimButler it was found that Gen2 {{calexp_camera}} is passed as an {{ImageF}} in {{ci_hsc}}, whereas in policy an {{ExposureF}} is listed. Modify the latter."
Answer: 278.0

User story: "Measurements of TE1 and TE2 are small numbers ~1e-6 and are truncated to 0.00 when displayed in SQuaSH."
Answer: 121445.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: "Before shipping the turnkey system to Tucson, a burn-in test must be run for 48 hours. This will require modification of the simple SAL message emulator used for in-house testing. The new emulator should include occasional start-ups and shut-downs of the ATS DM system, as well as randomly draw image_ids/catalog names from a set of 100 pre-triggered in the DAQ (triggering the images is not necessary for this test, and is only realistically done when Tony's CCS system is running as well.    As well as proper logging, the system should issue a 'result set' log report every time it is shut down."
Answer: 9920.0

User story: "In Gen3, we're planning to just persist Detectors with Exposures to make each Exposure more self-contained and avoid complex modify-on-load code (which would have had to get more complex than what we have now to handle camera versioning).  This means we need a way to save a Detector inside an Exposure, and at least at present, that means making it inherit from {{afw::table::io::Persistable}}.     "
Answer: 237573.0

User story: "Summarize low-level processing details for the operations team and add it to   https://confluence.lsstcorp.org/display/DM/S18+HSC+PDR1+reprocessing "
Answer: 19895.0

User story: The Dev Guide suggests we use the following:    {code}  .. bibliography:: local.bib lsstbib/books.bib lsstbib/lsst.bib lsstbib/lsst-dm.bib lsstbib/refs.bib lsstbib/refs_ads.bib     :encoding: latex+latin     :style: lsst_aa  {code}    However, when I tried this with a recent sphinxcontrib-bibtex, I get:    {code}  /Users/jds/Projects/LSST/docs/dmtn/031/index.rst:508: ERROR: Error in "bibliography" directive:  invalid option value: (option: "encoding"; value: 'latex+latin')  unknown encoding: "latex+latin".    .. bibliography:: lsst-texmf/texmf/bibtex/bib/refs_ads.bib     :style: lsst_aa     :encoding: latex+latin  {code}    I think this is due to changes upstream (I didn't track it down fully, but I note that both sphixcontrib-bibtex and pybtex have been making changes to the way they handle encodings in recent releases).    Simply removing the {{:encoding:}} line works fine for me.
Answer: 283547.0

User story: "As discussed in DM-14328 we need to specify a new environment in {{lsst.verify}} called LDF from which we will gather the following variables and add them as metadata to the verification job.  {noformat}  - ``DATASET``: the name of the dataset processed, e.g 'HSC RC2'  - ``DATASET_REPO_URL``: a reference URL with information about the dataset  - ``RUN_ID``: ID of the run in the LDF environment  - ``RUN_ID_URL``: a reference URL with information about the run  - ``VERSION_TAG``: the version tag of the LSST software used, e.g. 'w_2018_18'  {noformat}"
Answer: 20483.0