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: "Add {{Registry.getRegion(DataId) -> sphgeom.Region}} that returns the intersection of all regions associated with the {{DataUnit}} in the {{DataId}}."
Answer: 34627.0

User story: "DM-14714 also fixed this (the query for this is {{SELECT sourceId, objectId, blobField FROM Source WHERE objectId = 386942193651348 ORDER BY sourceId;}}, and I verified that the blobFields returned do have backslashes)"
Answer: 100.0

User story: "Document the as-is process of HSC biweekly and PDR1 reprocessing. Publish as a DMTN. "
Answer: 17241.0

User story: "<USER>(NAOJ) writes:  {quote}  the rotator LEDs have already been covered, and we have to uncomment [this|https://github.com/lsst/obs_subaru/blob/master/python/lsst/obs/subaru/strayLight/yStrayLight.py#L91].    It should be something like:  {code}      if exposure.getDateObs() >= datetime.datetime(2018, 1, 1):          return  {code}  but {{exposure.getDateObs()}} has to be replaced with a correct expression.    Koike-san found at least a field was affected by this bug around (ra, dec) = (157,  0).  {quote}"
Answer: 10079.0

User story: "ci_hsc failed the nightly build last night:     https://ci.lsst.codes/blue/organizations/jenkins/scipipe%2Fci_hsc/detail/ci_hsc/54/pipeline     "
Answer: 313.0

User story: "This ticket is to gather information for numerical data display for LSST data in SUIT.     Current Firefly displays 6 digits after decimal point by default. This may not be best for some data. We need to have a plan either specify the precision for each column in table data, or have a guideline for precision for different type of data, i.e ra, dec, magnitude, flux, error, ..."
Answer: 406804.0

User story: "We do not have every possible check enabled during C++ compilation, adding {{-Wextra}} to compilation flags should help us to uncover possible problematic code."
Answer: 2638.0

User story: "Now that YamlStorage has been implemented, we should use it."
Answer: 72964.0

User story: "Create a Jupyter notebook describing the results of reprocessing HiTS in DM-14259 along the same lines as those already in the [https://github.com/lsst-dm/ap_pipe/tree/master/notebooks] directory.    The notebook should contain basically the same figures and analysis as the previous notebooks (ie, we're not looking for new plots here) — it just needs to be updated to work with the latest version of the data processing.    (Edited to clarify this ticket is for the notebook created with an initial slurm reprocessing, not the Coming Soon reprocessing described in DM-14762 which involves new templates from DM-15080. The data used here is the same as what was intended for DM-14260 but ultimately was split between DM-14260 and DM-14261; i.e., the data used here is the present ap_verify_hits2015 dataset which includes [~<USER>'s original set of hits2014 coadds for templates.)"
Answer: 50425.0

User story: "Following DM-14259, we can run the AP pipeline on the VC using SLURM. Use that capability to process the HiTS 2014 data and build template coadds."
Answer: 159880.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 issues DM-15040 and DM-15041 have been raised, the release note need to be updated as follows:   * include issues in the Known issues section   * Specify that the 16.0 release meant to work using newinstall.sh 16.0 version, or using the corresponding (well defined) package baseline. "
Answer: 9117.0

User story: "Use framework in development on DM-14289 branch of qa_explorer, to create initial definition of DPDD-compliant Object table. "
Answer: 169934.0

User story: "[~<USER> and [~<USER> have both requested independently (the former quite a while ago) code that shows how to extract Footprints from SourceCatalogs without using afw code."
Answer: 121314.0

User story: "A preliminary answer to this question is in the pdf attached.  And its : likely unsignificant !    [^ozoneCTIO.pdf]"
Answer: 8757.0

User story: "we don't have variability and extendedParamer columns, choose other columns to satisfy the need.    Our case01 dataset is fairly sparse, all objects are futher apart than is supported by qserv near neighbor queries.    To allow this test to run, duplicate object 90030275138483 and change its {{ra_PS}} value slightly so that it will appear to be a usable near neighbor."
Answer: 4359.0

User story: "(From IPAC LSST group meeting today)    We would like to move to Java 10 for the deployment of Firefly servers in LSST, both just to keep moving forward, and specifically because Java 10 is substantially better-integrated with Docker and therefore more suitable for LSST's Kubernetes deployment environment.    This may trigger moving forward from Tomcat 7 to Tomcat 8 or 9, because the pre-built containers available at [https://hub.docker.com/r/_/tomcat/] do not include a Tomcat-7-for-Java-10 build. (Both Tomcat 8 and 9 have base containers available for both Java 8 and Java 10.)    We need to think about what to do with the IPAC development environments in this context, including testing and our K8s deployments. Ideally we would keep the {{dev}} branch compatible with both Java 8 and Java 10 for the foreseeable future.    This is clearly a FireflyCCB issue.    Note 8/28/2018 (Trey)- We don't plan to start writing Java 10 code until all the projects have gone though a deployment cycle.  Currently we want to be able to deploy on both Java 8 and Java 10 and the related Tomcats.  When all projects have deployed on Java 10 then we will start using Java 10 features."
Answer: 132479.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Current best thinking is that we can most conveniently both orchestrate & control resources in the mini broker by running each filter in a separate Docker container.    This is potentially tricky, because we obviously can't support n_filter times the total alert stream bandwidth flowing over the network. Likely, we get around that by sending a full copy of the alert stream to a limited number of hosts and then using inter-process communication between Docker containers on the host... maybe.    Other issues are things like how to start up new filters, how to keep track of how many alerts have been passed by each filter for a given visit, etc.    Come up with a straw-man design for how this might work. Either a proof-of-concept in code or a document describing the design is fine as a deliverable.  "
Answer: 45975.0

User story: "Represents July work to go through the FIXME integration test queries and determine if they are FIXME because they fail to parse, or if they fail to run. Fix these on separate tickets (each fix gets its own ticket & branch).    Fixes that require parser work will be fixed our new antlr4 parser and will be checked into the antlr4 integration branch (\{\{u/<USER>antlr4}}) until that branch is merged to master.    Fixes that do not involve the parser may be checked directly into master.    The output of this will be compared with [query pages in TRAC|https://dev.lsstcorp.org/trac/wiki/db/queries] (being ported to Confluence by [~<USER>), and stories to fix these stories will be created as appropriate."
Answer: 36171.0

User story: Investigate the performance of "standard" PSF and galaxy models when fitting idealized images using code written for DM-14810, to help determine which models are worth implementing and/or optimizing further.    PSF models: Single Gaussian, double Gaussian, single Moffat (and noisy images thereof)    Galaxy models: Single Sersic (disk- and elliptical-like), Exponential disk + Sersic bulge
Answer: 146741.0

User story: "This is a continuation of work started in DM-14334. Main goal of this ticket is to extend preflight solver with joins between skymap units and camera units so that we have more or less complete solution for building quantum graphs. "
Answer: 20052.0

User story: "This enables us to set it as the global default matcher."
Answer: 295270.0

User story: "Or rather, in the validation datasets used by lsst_ci.    Should use PS1 or Gaia stored rather than SDSS stored in a_d_n format.    Write an RFC to explain the change and see if anybody objects."
Answer: 53297.0

User story: "This was discussed in DMTN-031."
Answer: 13027.0

User story: "The convolved measurements on the undeblended sources are very useful, e.g., for photometric redshifts. However, they are not activated."
Answer: 3228.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: "On my laptop (running macOS), having worked around DM-15040 (by adding a {{-j}}):    {code}  $ eups list lsst_distrib -s     16.0+1       current v16_0 o_latest setup  $ bin/demo.sh  (elided)  $ bin/compare detected-sources.txt | head  $ bin/compare detected-sources.txt | head  Failed (absolute difference 4.56509e-10, relative difference 1.29849e-12 over tolerance 0) in column coord_ra.  Failed (absolute difference 1.61435e-11, relative difference 4.59182e-14 over tolerance 0) in column coord_ra.  Failed (absolute difference 1.25681e-10, relative difference 3.57483e-13 over tolerance 0) in column coord_ra.  Failed (absolute difference 1.90084e-10, relative difference 5.40671e-13 over tolerance 0) in column coord_ra.  Failed (absolute difference 1.30569e-10, relative difference 3.71386e-13 over tolerance 0) in column coord_ra.  Failed (absolute difference 4.01428e-10, relative difference 1.1418e-12 over tolerance 0) in column coord_ra.  Failed (absolute difference 3.93925e-11, relative difference 1.12046e-13 over tolerance 0) in column coord_ra.  Failed (absolute difference 3.15481e-11, relative difference 8.97331e-14 over tolerance 0) in column coord_ra.  Failed (absolute difference 4.99028e-10, relative difference 1.4194e-12 over tolerance 0) in column coord_ra.  Failed (absolute difference 3.41061e-10, relative difference 9.70072e-13 over tolerance 0) in column coord_ra.  $ bin/compare detected-sources.txt | wc -l   98656  {code}    ...that's a failure.    Note that I obtained this test data by running:    {code}  curl -L https://github.com/lsst/lsst_dm_stack_demo/archive/16.0.tar.gz | tar xvzf -  {code}    so it should correspond to v16.0 of the codebase."
Answer: 47378.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 announced at https://community.lsst.org/t/logging-now-defaults-to-stdout/2331  CmdLineTasks logging now sends to stdout instead of stderr. Update generateDax.py in [pegasus_workflow|https://github.com/lsst-dm/pegasus_workflow] for this change."
Answer: 7275.0

User story: "In the review for DM-14334 it looked like some utility classes for DataUnits could be helpful.  In particular:   * We once had a DataUnitTuple class that defined a sort order and a de-duped set of value column names, but dropped it when we added the new DataUnit class.  Looks like we should create a new one that builds on the DataUnit class and TopologicalSet.   * We should at least consider having a custom Data ID class, both to make it hashable and hence usable as a dict key and as a place to add integer packing in the future."
Answer: 230346.0

User story: "For JSON-formatted table schemas for presenting metadata, the following W3C Recommendations:                        [https://www.w3.org/TR/tabular-metadata/|https://www.w3.org/TR/tabular-metadata]                        https://www.w3.org/TR/tabular-data-model/    which are dialect of the W3C standard:                        [https://www.w3.org/TR/json-ld/]    From the VOTable-compliant data model, generate and output XML for return to client upon request header:          Accept: application/xml                        or         Accept: application/json               "
Answer: 168251.0

User story: "Map the VOTable Specification into JSON equivalent using JSON Schema.    VOTable 1.3:    [http://www.ivoa.net/documents/VOTable/20130920/REC-VOTable-1.3-20130920.html]    JSON Schema Specification:    [http://json-schema.org/specification.html] (upgrade to Draft-06 [alpha] if necessary vs Draft-04 in DAX today)    Official download page: https://pypi.org/project/jsonschema/     "
Answer: 30359.0

User story: "Work with SLAC staff to collect performance data from initials runs, and begin analyzing results."
Answer: 1337.0

User story: "We have decided to change how module and package documentation directories are used. The original design was to have module and package documentation directories for all packages (unless the package did not provide Python modules). The new design is to have one type of directory, but not both. This de-emphasizes the role of EUPS and packaging in our user documentation, and is future proof-for a possible mono-repo refactoring of the LSST Science Pipelines.    This means that module documentation directories now need to provide information about the project (Git repository, Jira component).    This ticket is to update the {{stack_package}}  template (https://github.com/lsst/templates) and DMTN-030 technote (https://github.com/lsst-dm/dmtn-030) with this new design.    Changes to the Developer Guide documentation will be handled in DM-14852 and changes to https://github.com/lsst-dm/pipelines_lsst_io will be handled in DM-11216.  "
Answer: 11371.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_modelfit has some issues with Eigen 3.3.4. I am making this a separate ticket from DM-14305 in hopes that these can be fixed in a way that is backwards compatible.    The first issue is that this does not compile:  {code}  ndarray::asEigenMatrix(*ix) = component._mu      + std::sqrt(_df/rng.chisq(_df)) * (component._sigmaLLT.matrixL() * _workspace);  {code}  but the solution to that is trivial: swap {{component._sigmaLLT.matrixL()}} and {{\_workspace}}, though [~<USER> suggested a solution that reduces duplication with nearby code.    A more serious concern is that the following code in {{TruncatedGaussian.cc}} {{TruncatedGaussian::maximize}} raises an assertion error that a matrix is empty when {{running tests/test_truncatedGaussian.py}}:  {code}  Eigen::FullPivLU<Matrix> solver(G.topLeftCorner(n - k, n - k));  {code}  To fix that problem [~<USER> suggests returning a vector of all zeros if n == k."
Answer: 137.0

User story: "Enable auditing and update code to provide the LDF monitoring system information for displaying ATS component state."
Answer: 761987.0

User story: "assisted in debugging issues with the k8s cluster not starting containers."
Answer: 1.0

User story: "Various needed improvement/additions to xCAT."
Answer: 1.0

User story: "Set up test mounts to see what issues there may be in using SMB mounts on the Kubernetes commons."
Answer: 5.0

User story: "Add tracking modes to LTD Keeper so that an Edition can track the latest EUPS release tags of different types:   * {{vX_Y}} — {{eups_major_release}}   * {{w_YYYY_WW}} — {{eups_weekly_release}}   * {{d_YYYY_MM_DD}} — {{eups_daily_release}}    It might also be prudent to, at the same time, provide variants for the Git-based tag names:     * {{X.Y}} — {{eups_git_major_release}}  * {{w.YYYY.WW}} — {{eups_git_weekly_release}}  * {{d.YYYY.MM.DD}} — {{eups_git_daily_release}}"
Answer: 7293.0

User story: "I've accumulated a number of minor changes in display_matplotlib:   * qt5 is an interactive backend   * mask plane composition is done wrong   * export savefig to the afwDisplay interface   * support Buffering()   * Be smarter about the shape of zoomed images"
Answer: 184604.0

User story: "Add support for additional third-party Python packages used with the LSST Science Pipelines for use with intersphinx (configured via documenteer).    There's a known request for pandas. This ticket will determine if there are other eligible packages."
Answer: 85.0

User story: "The version of the EFD used for analysis within the DM subsystem has different use cases and requirements than the raw EFD does.  Produce a document that outlines the major DM use cases and the implied requirements thereof."
Answer: 83565.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: While doing additional testing of DM-14510, I noticed that the astrometry model fit could be thrown off by doing a line search during the initialization {{DistortionVisit}} fit step. This reminded me that I haven't implemented the separate "Visit" and "Chip" fitting option for Photometry: it may help things by pushing the toward the global minimum on the first step (as it does in astrometry). It should be very easy to implement.
Answer: 21960.0

User story: "The sims team would like an automatically built weekly sims version that is built on the weekly build of {{lsst_distrib}}.  They would like the result to be a binary distribution that would allow end users to install a full stack of sims plus DM dependencies that are all consistent with the weekly build.  I.e.  {code}  $> eups distrib install lsst_sims -t w_2018_13  {code}    This is currently possible to do by hand, but it would be useful to them to have it automatically build.  They are very clear that a failing {{lsst_sims}} weekly build should not imply a failing {{lsst_distrib}} build."
Answer: 109648.0

User story: Add the ability to exclude named packages and modules from the piplines.lsst.io documentation through a "skip" field in the package-toctree and module-toctree directives.    The "skip" field takes a comma-delimited list of names.    This field is useful for temporarily removing packages that break the documentation build.
Answer: 303.0

User story: Make _static/ directories optional for stack documentation and technotes in Documenteer-based Sphinx configurations.    Also make the "statics" field optinal in {{manifest.yaml}}.
Answer: 55.0

User story: "display_ds9 doc/status has already been done, so I will go through and upgrade to numpydoc status. "
Answer: 376665.0

User story: "Create a technote describing the requirements and design for notebook-based reports. These reports are initially described in the DM-14551 epic."
Answer: 62856.0

User story: "Integrate and test the HeaderService with new ts_xml tag ManCtrl_MPD_AuxTel in preparation for the ACCS MCM/OCS Bridge for Spectrograph Integration Test "
Answer: 31714.0

User story: "Update the AT Header Service template to conform to undefined values as described in Pence et al 2010.    From Pence et al 2010, the standard for null/empty/undefined should be as follows:  Note that there is a subtle distinction between the following three keywords:    {noformat}  KEYWORD1= '' / null string keyword  KEYWORD2= ' ' / empty string keyword  KEYWORD3= / undefined keyword  {noformat}    The value of {{KEYWORD1}} is a null, or zero length string whereas the value of the {{KEYWORD2}} is an empty string (nominally a single space character because the first space in the string is significant, but trailing spaces are not). The value of {{KEYWORD3}} is undefined and has an indeterminate data type as well, except in cases where the data type of the specified keyword is explicitly defined in this standard.    "
Answer: 155624.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: "Include SettingsApplied event from the atHeaderService"
Answer: 31724.0

User story: Schema naming conventions changed from "."-separated with no case consistency to "_" and camelCase with the introduction of meas_base.  I remember writing the new conventions down somewhere, but the first two places I looked:     - afw::table::Schema class docs     - afw::table overview page in Doxygen    ...document the old convention.         Fix those, ideally by locating the original text (maybe Confluence somewhere?) and transferring it to those locations.     
Answer: 1254.0

User story: We currently have the following set of names for the calib_* flags that get propagated to source catalogs:   * *calib_detected*   * *calib_psfCandidate*   * *calib_psfUsed*   * *calib_psf_reserved* (changed from *calib_psfReserved* on DM-12207 in [this commit|https://github.com/lsst/pipe_tasks/commit/1724e04014047d69032f4aa7b2e8702b9b98942f])   * *calib_astrometryUsed*   * *calib_photometry_used* (changed from *calib_photometryUsed* on DM-12207, in [this commit|https://github.com/lsst/pipe_tasks/commit/7a868d53137079c555e9569c55fd87337c0a8477])   * *calib_photometry_reserved* (changed from *calib_photometryReserved* on DM-12207 in [this commit|https://github.com/lsst/pipe_tasks/commit/1724e04014047d69032f4aa7b2e8702b9b98942f])    I.e. there is a mixture of _underscore and camelCase_ for the third (final) "descriptor", making it difficult to remember which standard to use when trying to select on a given flag.  These should all be homogenized and, given the recent changes in this direction noted above, I believe the preferred choice is the _underscore_ standard.    A change in the flag names will affect any current user scripts that select on these flags.  To prevent scripts from breaking, it may be desirable to set a (temporary?) alias (although this was not done along with the DM-12207 changes and there was no uproar that I'm aware of).
Answer: 73594.0

User story: New tags have been created for the "ACCS MCM/OCS Bridge for Spectrograph Integration Test" in Tucson. The software for these new tags needs to be built and tested in the NCSA L1 TestStand before the Tucson integration activity.  h1.  
Answer: 31842.0

User story: "Holoviews is now no longer displaying correctly."
Answer: 21893.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2018_30 RC2 outputs from DM-14988"
Answer: 56595.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp  # matchedVisitMetrics.py  # validateDrp.py   # reportPerformance.py   # dispatch_verify.py    with the w_2018_26 RC2 outputs from DM-14689"
Answer: 1680.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_28. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 21898.0

User story: "Working with admins, etc to get initial setup of production hardware and services for the NCSA Data Backbone.  Includes initial internal testing."
Answer: 96332.0

User story: "16.0 is out, so I can remove all of the Python 2 accommodation from the JL environment."
Answer: 5758.0

User story: "The {{Detector}} objects are unable to find the {{Camera}} wherein they dwell, meaning that _e.g._ {{ccd.transform(pos, camGeom.PIXELS, camGeom.FIELD_ANGLE)}} is impossible (you need a camera), and the functionality requested in DM-14932 cannot be implemented given only a {{Detector}}.    Please add _e.g._ {{detector.getCamera()}} to the {{Detector}} API.  This may require moving {{Camera}} back into C++."
Answer: 149972.0

User story: "Initial investigations on using the Science Pipeline payload from within the Singularity containers.  Try to run some small examples on our LSST machines. "
Answer: 34288.0

User story: "Test ability for heapster (Kubernetes monitoring tool) to integrate with the LDF monitoring environment.  "
Answer: 7.0

User story: "We would like to make the HeaderService configurable as much as possible via an external configuration (YAML) file.    The configuration should enable:   * Control general behavior of the HeaderService   * Define the origin of the telemetry and the header keywords associated with it.   * Define the event at which the telemetry/Event should be read.   * Define the collection start/end collection events   * The HeaderService to automatically subscribe to all relevant channels for Events/Telemertry    In addition we would like the HeaderService to:   * be re-factored into it own class.   * automatically update the keywords from the telemetry received. "
Answer: 36140.0

User story: "We have seen issues with some clients failing to communicate with qserv after upgrade to mariadb 10.2.14. Two notable cases are JDBC (see DM-14924) and nagios test script which is Perl script using DBI.    JDBC workaround was to downgrade to older version of JDBC. I think {{usePipelineAuth}} connection attribute is a suspect but I remember Kenny was playing with in recent JDBC is and it did not help much, so there may be other reason for it.    Nagios script has trouble on Ubuntu but works fine on CentOS7, I think the difference is due to older version of mysqlclient installed on CentOS7 (I had used system-installed Perl DBI)."
Answer: 8864.0

User story: "Provide general support for early use of the kubernetes cluster for May 2018. Covers small emergent tasks. Staff includes Matt Long & Jake Rundall."
Answer: 40533.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: The ticket echos one of the tasks listed by C. Stubbs on [https://confluence.slac.stanford.edu/display/LSSTDESC/AuxTel+effort]    "build system to interrogate and delivery satellite-based ozone measurements, with appropriate metadata and uncertainties"    A first version of the script has been written which retrieves from the NASA server the ozone value for a given date and given site.    It could be further expended to access other parameters.
Answer: 237951.0

User story: "We are working with [~<USER> at SLAC to benchmark AP performance against our system and look for areas of improvement."
Answer: 51501.0

User story: "Set up r10k, a toolset for deploying Puppet environments and modules, Build sample, devise deployment plan, and build testing infrastructure.     "
Answer: 1365.0

User story: "Given an accurate boresight and rotator angle from a camera, we should be able to construct our best initial estimate of the WCS for a sensor by combining that information with our own camera geometry, as this will probably produce better results that relying on any WCS provided directly by the camera.  In fact, for LSST, it's not clear that there even will be a sensor WCS provided directly by the camera, because LSST raw data has amps in different HDUs and no full-sensor HDU that could unproblematically hold a full-sensor WCS.    To do without using astshim code directly, we should provide utility functions in afw with something like the following signatures:  {code:java}  TransformPoint2ToSpherePoint makeIntermediateWorldCoordsToSky(      SpherePoint const & position,  // (ra, dec) that corresponds to FIELD_ANGLE origin      Angle rotation // rotation about FIELD_ANGLE origin  );    std::shared_ptr<SkyWcs> makeSkyWcs(      TransformPoint2ToPoint2 const & pixToIwc,      TransformPoint2ToSpherePoint const & iwcToSky  );{code}"
Answer: 18942.0

User story: "Hold initial discussions with SLAC staff for tsting requirements, and set up the database system for testing."
Answer: 10261.0

User story: "* *Monitoring the atmospheric throughput at Cerro Tololo InterAmerican Observatory with aTmCam*    *[https://arxiv.org/pdf/1407.7047.pdf]*         T. Li paper reports two campaigns of real time monitoring of PWV and AOD at CTIO. The points relevant to Aux.Tel are the followings :   # PWV can change by a few millimeters over one night and mostly decreases over time on any given night   # PWV measurement precision : Assuming there is no variation in 3 minutes, the precision of the measurement is given by the sigma of the black histogram : 0.3 mm uncertainty on the measurement.   # From their dataset, the authors conclude that a 1 mm monitoring implies an hourly sampling.     #      The authors report no detection of spatial gradient (i) From MERRA-2 0.1 mm could be expected, which is below the sensitivity of their observations.    !Capture d’écran 2018-06-28 à 12.06.23.png!"
Answer: 10466.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 TE1, TE2 metrics have expected values on the order of 10^-6.  The current SQuaSH display defaults to showing things on the order of 10.  Scrolling in 6 orders of magnitude isn't really practical.  It's thus not possible to use the visualization to understand the performance.    Please adjust the default display range either   (a) based on the range of values, with an additional requirement to include 0  (b) on a hard-coded fixed range."
Answer: 61668.0

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

User story: "With the {{v16_0}} release, the LSST Science Pipelines don't support Python 2.7 anymore. Thus we need to remove references to Python 2.7 from the installation documentation."
Answer: 1422.0

User story: "Layout architecture for moving monitoring services into VM's for better durability and more efficient use of resources.  This will allow the current lsst-monitor01 host to be used for other LSST operational needs.  "
Answer: 1.0

User story: "For some reasons {{ctrl_orca}} is missing the {{bin}} folder, at least in recent releases (e.g. docker images v15, w_2018_23, ...).  Usually a {{bin}} folder is created for packages with a {{bin.src}} folder during the build process. But the {{bin}} folder is not made in {{ctrl_orca}}; {{rewrite_shebang}} is not run in the build process.   This is also true in {{lsstsw}} build and the shared stack in {{/software}} on LSST machines.  Manually {{scons}}-ing it works. "
Answer: 12932.0

User story: "Use Local Volume API for Qserv data persistence instead of hostPath"
Answer: 11623.0

User story: Add {{disableCc=True}} to {{SConstruct}} to indicate that this is a pure-Python package and one does haven't to worry about having to load the correct gcc just to "compile" it (which is mainly about install {{bin.src}} into {{bin}} accounting for Mac OS X SIP.     {code}  scripts.BasicSConstruct("validate_drp", disableCc=True)  {code}
Answer: 756508.0

User story: Update all the python modules in the obs_test package so they have numpydoc doc strings instead of doxygen. Make sure the entire package sphinx docs can be built.    Useful references:      [https://community.lsst.org/t/pipelines-package-docs-hack-day-instructions/2742]  --> start at "Beginning the Numpydoc conversion, one module at a time"     [https://developer.lsst.io/python/numpydoc.html] 
Answer: 250740.0

User story: "The goal is to include findings regarding handling data (file transfers, cleanup) in Pegasus WMS in the technote describing detailed Pegasus evaluation."
Answer: 4256.0

User story: "The goal is to start a technote for describing findings regarding job clustering capabilities of Pegasus WMS in greater detail."
Answer: 2696.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: "Pegasus WMS supports data management (staging data in and out, cleanup unused files, etc). The goal is to explore those capabilities in details and find out if they satisfy needs of the batch production service, e.g.:  * what architectures are supported (shared vs. non-shared filesystems),  * what level of control over data transfer/cleanup is available for an operator."
Answer: 2706.0

User story: "For efficiency and scalability reasons, a need to partition a large workflow into set of smaller ones may arise during production. The goal is to find out how well this feature is supported in Pegasus WMS."
Answer: 2592.0

User story: "Due to an overhead during a job submission, in certain situation grouping jobs in a cluster is a more efficient approach. As Pegasus WMS supports job clustering, the goal is to investigate its capabilities in that area and find out to what extent they satisfy needs of batch production service."
Answer: 2592.0

User story: "The description of the SuperTask design is distributed among various sources (Confluence pages, technotes). Additionally, these documents are being quickly rendered obsolete due to rapid changes in Gen3 Butler design.  Hence, the best place to find out what is SuperTask current design is to look directly at its source code. The goal is to read through the SuperTask code and find out what features are currently supported."
Answer: 2593.0

User story: "Includes reading and responding to Slack discussions, design documents, attending any Gen3 meetings, etc. by folks at NCSA."
Answer: 4412.0

User story: "Meetings with K-T, <USER>and <USER>to discuss Data Backbone Services generically then focussing on the LSE-61 requirements.    Reading multiple high level documents, understanding why certain requirements were or were not linked to Data Backbone Services, etc     Create spreadsheet with LSE-61 requirements for initial Data Backbone Services Requirements."
Answer: 3.0

User story: "Architecting how we want to handle incoming metrics data from sources that do not have built in buffering capabilities (eg. data not flowing in via telegraf).  "
Answer: 112345.0

User story: We're not consistent about indentation (especially in lists).    We have a lot of places where we have a "tables" section that is a dict that is only permitted to have one entry, and the entry always has the same key as the node that contains the "tables" section.  We could probably remove some levels of indirection here.
Answer: 162573.0

User story: "Explored best method of encrypting traffic between clients and the metrics database to ensure safe communication when traveling across public networks.  Determining where in encryption was necessary and where it wasn't (if there were places that didn't need it).  "
Answer: 1350.0

User story: "Timing the match scoring and matching methods would be useful in the context routing out slow downs in the association step of ap_pipe."
Answer: 113754.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This ticket will be necessary to testing the informedShape algorithm in [DM-13809|https://jira.lsstcorp.org/browse/DM-13809]. It will involve  * Spending some time assessing how Pybind11 handles unique_ptrs and based on the outcome evaluate if that is still the best choice for the c++ side of the class.  * Wrap the StarGalaxyPrior  * Wrap the GalaxyPrior class, which is a datamember of the StarGalaxyPrior  * Wrap the Prior on star v galaxy from [Dm-14892|https://jira.lsstcorp.org/browse/DM-14892]"
Answer: 191888.0

User story: "Use the info determined in [DM-14891|https://jira.lsstcorp.org/browse/DM-14891] to code a corresponding c++ class for use in the StarGalaxyShape prior."
Answer: 226404.0

User story: "Given that Sophie has done a lot of work on determining star v galaxy probabilities, work with here to determine an appropriate form for a Probability of an object being a star vs a galaxy given magnitude. This may involve discussions with Yusra as well, as she has some experience in this area as well."
Answer: 191910.0

User story: "The Prior of galaxy shapes should be converted to to use calibrated magnitudes instead of fluxes.  This ticket will:  * Change the script used to extract parameters from catalogs  * Update the code that generates the Gaussian mixture models and boxcox parameters  * Update the parameters determined above in the C++ of the Galaxy Prior  * Change the prior code to work in terms of magnitudes instead of fluxes (mainly adjusting inputs and derivatives)"
Answer: 226418.0

User story: "A simple python script that produces atmospheric transparency curves from a table of parameters (from MERRA-2 at MaunaKea)    [^atmosim3.py]"
Answer: 13159.0

User story: "Replace visit_id with raft list in add_job call."
Answer: 20590.0

User story: "ipyaladin builds fail; something to do with newer webpack, I think."
Answer: 4317.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp  # matchedVisitMetrics.py  # validateDrp.py   # reportPerformance.py   # dispatch_verify.py    with the w_2018_24 RC2 outputs from DM-14688"
Answer: 14.0

User story: "Update Qserv version with the last container image in Qserv deploy tool"
Answer: 2604.0

User story: "One single glossary of terms for data management is needed, especially for commissioning teams and science collaborations using the data management software, service and data product.  Several DM glossaries exist already:     [https://confluence.lsstcorp.org/display/LSWUG/DMS+Glossary]    [https://confluence.lsstcorp.org/display/LSWUG/Astro+Glossary]    [https://dev.lsstcorp.org/trac/wiki/glossary]    [https://dev.lsstcorp.org/trac/attachment/wiki/Glossary/EAGlossary.pdf]    Project-level acronyms: [http://ls.st/Document-11921*]    Project-level glossary: [http://ls.st/Document-14412*]       The goal is to consolidate these and provide one single glossary."
Answer: 135600.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It seems that there are two commonly used conventions to define the “ellipticity”, which Bosch et al. 2017 refer to as the “distortion” and the “shear” (see Appendix 3 of [https://arxiv.org/abs/1705.06766] , particularly footnote 8 ). This difference in definition is also described in the wikipedia article [https://en.wikipedia.org/wiki/Gravitational_lensing_formalism#Measures_of_ellipticity] . It seems that the LSST pipeline is using the “distortion” definition based on the discussion in Bosch et al. 2017, and this appears to be confirmed by Equation 2 of Mandelbaum et al. 2017 [https://arxiv.org/abs/1705.06745] . The formula currently in `validate_drp` looks to be using the “shear” definition, e.g., slide 8 of this presentation by Catherine Heymans [http://www.roe.ac.uk/~heymans/KSBf90_for_DUEL/Download_Lecture_Notes_files/Lecture1_CH.pdf] . That same formula for the “shear” case also appears in the wikipedia article with the epsilon symbol. Meanwhile, it seems that the SRD is using the “distortion” definition (equations 10 and 11, [https://docushare.lsst.org/docushare/dsweb/Get/LPM-17] ). Therefore, it seems that for consistency, that we would also want to use the “distortion” convention in `validate_drp`. In that case, I think we would have  {code:python}e = (I_xx - I_yy + 2j*I_xy) / (I_xx + I_yy)  e1 = np.real(e)  e2 = np.imag(e){code}  Here are the relevant line in validate_drp:    [https://github.com/lsst/validate_drp/blob/2df8e11de267ce4944ad0a12032c95bc244397fa/python/lsst/validate/drp/util.py#L95]"
Answer: 16271.0

User story: The "new" standard for the DM Stack processing is to use HTM style catalogs intead of astrometry.net formatted catalogs.  The processing of the {{validation_data_hsc}}    1. [x] Provide HTM reference catalogs for the {{validation_data_[cfht,decam,hsc]}}.  DM-13701  2. [x] Updating the processing configs to use these catalogs.  3. [x] Update the HSC processing to include the transmission files.  4. [x] Update the curated processed files based on these new reductions.  5. [x] Update the examples in {{validate_drp/examples}} and the equivalent {{lsst_ci/scripts}} to use these catalogs.  6. [x] Compare SRD performance with old-style and new-style catalogs to look for and characterize any significant differences.  
Answer: 261088.0

User story: "Start using something that smells like MySQL rather than sqlite for Hub session db."
Answer: 50395.0

User story: "[~<USER> has sent me an initial set of requirements for the Data Backbone Services. I will put them in the model and upload an initial draft to DocuShare."
Answer: 179.0

User story: "testQueryAnaGeneral.cc causes a warning:    Comparison between signed and unsigned integer expressions return left == right.    Probably in `BOOST_REQUIRE_EQUAL(first->subChunkIds.size(), 3);` ought to be 3u."
Answer: 1398.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: "Provide VOTable-compliant output so that VO tools like astroquery library (or TopCat) can query dbserv using TAP to get back results in VOTable (XML) format.  After this work, dbserv will accept the new HTTP option:                 Accept: application/xml    From IVOA:  although there is motion to support JSON as acceptable alternative to XML, it's imperative for dbserv to support existing XML-based standards for backward-compatibility.      For better performance in Python-land, especially for large results, JSON output will continue to be provided, so to avoid the unnecessary data conversions from sending/receiving ends.     At a minimum, DAX must provide tabular output, in VOTable format, per TAP in regard to requests on TAP_SCHEMA.schemas, TAP_SCHEMA.tables, and TAP_SCHEMA.columns.  For DAX, TAP_SCHEMA is logically mapped to MSDatabase in metaserv.  Under MSDatabase, two database schemas are supported: DS_wise, W13_sdss_v2.     "
Answer: 249487.0

User story: "Thereby implementing RFC-491.    Also implement the speedup discussed on that RFC. "
Answer: 312709.0

User story: Allow preselection of default Hub container size via environment variable (e.g. so "medium" rather than "small" can be the default).
Answer: 101200.0

User story: "Add to the HeaderService the option of reading the argparse config options and the source of telemetry from an external YAML file."
Answer: 11948.0

User story: "This ticket is to write documentation that enables developers to successful contribute to documentation for the LSST Science Pipelines:    - How to write documentation in the system.  - How to build LSST Science Pipelines (pipelines.lsst.io and single package) documentation locally  - How to build pipelines.lsst.io from Jenkins."
Answer: 51943.0

User story: "Updates to the first LDM-639 public draft"
Answer: 68896.0

User story: "The {{display_ginga}} package has configuration issues that prevent it being built.    Specifically, there is a missing import and a missing package setup."
Answer: 1019.0

User story: {{afw.display}} provides methods for setting mask plane colors and transparencies. These should be "sticky" in the display_firefly backend, meaning that once they are set for a Display object, they should be applied when an image is sent again to that display.    The display_firefly backend also needs to ignore masks whose color is set to "ignore" or "IGNORE".     Related to this, {{afw.display}} provides {{setDefaultMaskTransparency}} and {{setDefaultMaskPlaneColor}} which are used when Display instances are created. Fix a small bug in {{setDefaultMaskTransparency}} and verify that both of these work with the display_firefly backend.
Answer: 74952.0

User story: "Convert alert_stream mini-broker components deployment instructions to work with Kubernetes."
Answer: 14851.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 improvements are available for the Firefly parts of [~<USER>'s intro-with-globular notebook used in the Lyon 2018 hands-on session and later demos.   * Define the Display so the proper URL is available before the IFrame cell, so that `lsp-demo.lsst.codes` need not be hardcoded into the notebook   * Dial down mask transparency via afw.display   * Show how the {{firefly_client.plot}} convenience module can upload the catalog and overlay on the images."
Answer: 268.0

User story: "Things are breaking with 0.9.0 of JupyterHub; get_pod_manifest() no longer works like it did.  This needs investigation and fixing."
Answer: 3224.0

User story: Review comment on DM-14811: "This may be out of scope for this issue, but since we know which tables any of our views will depend on, could we make the creation of just those tables trigger view creation?". The answer is yes, but it is tricky because:    * Schema.addTable doesn't know about the relations.  * SQLAlchemy DDLEvents trigger on single entities only.    For the latter a solution would be to trigger view creation / dropping on all relations. This may duplicate some calls, but (in case of drop in particular) is probably the right thing to do.  This still needs a solution to the first point, developing that is part of this ticket.
Answer: 172922.0

User story: "When using a coarse pixelization for SkyPix join tables, spatial joins between Visit/Sensor and Tract/Patch can include many entities that don't actually overlap.  Preflight should be able to handle this, but this is inconvenient for users interested in querying the database directly, and having to implement post-query filtering in all APIs that interact with spatial join tables is tricky.    We could address this in-database in SQLite by using  {{sqlite3.}}{{create_function}} to define a per-connection UDF in Python that we could use in those views to further filter those join tables based on actual {{sphgeom.ConvexPolygon}} overlaps.    While this would not be portable to other RDBMSs, I am not proposing that we *require* registries to do this additional filtering, and of course many other RDBMSs are likely to provide similar UDF functionality, albeit through some other interface.  Most importantly, I think it's might be good for our design process to start adding some non-portable functionality in order to make sure our design lets us separate it from portable code (i.e. by adding functionality to SqliteRegistry instead of SqlRegistry)."
Answer: 690441.0

User story: "Test WISE metadata and update the references to WISE tables to use logical db."
Answer: 1071.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Add the P1/P2 "Principal Color" axes (à la Ivezić et al. 2004AN....325..583I) to the stellar color-color plots.      In more detail, for each principal color, we compute the mean offset and standard deviation for the wired "canonical" coeffecients to the P2 and P1 axes. We also fit for these for the given data. These two sets of axes should be added to the color-color plots as they provide useful information about the stellar locus/populations. A shift of the P1 line would indicate a fundamental shift in the color "locus", whereas a shift in the P2 axis indicates a shift in the position of the highest density of stars which is how the origin of the P1/P2 plane is selected (i.e. this would not likely consist of a fundamental "offset" in the colors, but rather be reflective of the distribution of stars along that particular pointing. Such a shift does not affect the mean or standard deviation in the statistics shown on the histograms).
Answer: 162480.0

User story: As we discovered in the SuperTask conversion kickoff meeting, writing (e.g.)  {code:java}  myInput = ConfigField(      dtype=InputDatasetConfig,      doc="Input image dataset type definition.",      default=InputDatasetConfig(          name="name",          units=("Camera", "Visit", "Sensor"),          storageClass="Exposure"      )  ){code}  is much too verbose.    Add custom {{Field}} objects so the above can be written as  {code:java}  myInput = InputDatasetField(      doc="Input image dataset type definition.",      name="name",      units=("Camera", "Visit", "Sensor"),      storageClass="Exposure")  ){code}
Answer: 53133.0