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: "There are one or two white papers to draft - starting with demise of the file system. If that ends up large the reference architecture will have to be in another.     I will agree with Jonathan and TIm how to out whitepapers in the build system then set up repos for these..    Also there should be a DMTN on the LSST cast in the reference arch"
Answer: 204997.0

User story: "Now that the shared stack has been rebuilt with the new conda environment, the minimum supported versions in the python, numpy, astropy, matplotlib, and scipy stub packages have to be changed to match the new environment."
Answer: 5506.0

User story: "There are several errors in the setup.py file for TunableLaser CSC.   * package attribute should be packages   * The namespace should lsst.ts.tunablelaser not lsst.ts.laser."
Answer: 101269.0

User story: "Possibly more generally create a namespaced secret and stuff sensitive data in there rather than directly into the Pod environment in the spawner."
Answer: 15094.0

User story: "Integrate and test the MTAOS usage of OFC's controller interfaces."
Answer: 7326.0

User story: "[~price] noticed that the use of {{unsigned}} (== uint32, usually) as the index type for Eigen matrices in jointcal _might_ be a problem:   * Eigen docs appear to want a signed integer;   * our number of sources in some of our processing is approaching 2^31.    There's no hard evidence that this is what's causing the segfault we're seeing when processing the (larger, still-proprietary) HSC UltraDeep, and since {{unsigned}} should be able to handle 2^32, I'm personally skeptical that this is the problem.  But it should be easy to fix, and a good thing to do regardless, especially for the first reason.    {{std::ptrdiff_t}} is probably the right choice to use instead - that will be a signed integer as large as the pointer type (i.e. int64, usually), and hence the largest unsigned type that's actually usable as an index.     "
Answer: 39899.0

User story: From [~<USER> at [https://lsstc.slack.com/archives/C2JPT1KB7/p1553801514017200]:  {quote}For each run there were a bunch of  ```DELETE FROM "PatchSkyPixJoin" WHERE "PatchSkyPixJoin".tract = :tract_1 AND "PatchSkyPixJoin".skymap = :skymap_1 AND "PatchSkyPixJoin".patch = :patch_1```  statements which at first glance seem to be coming from the pipeline. If they are from the pipeline (instead of the gen3.py or other bootstrap codes), then we should talk sometime about why there is a delete.  {quote}  These tables should be inserted into in gen2convert, but not deleted from.  They should not be modified at all during processing.  It's possible I'm just clearing subset of a table before inserting into it, which would mean in this case these DELETEs are no-ops because there are no matching record.  If that's the case, we might be able to ignore this.
Answer: 273941.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 T&S group would like some added privileges for their S3 bucket credentials.  Specifically, they would like to execute {{aws s3 website s3://sal-topic-registry --index-document index.html}}.  This is so they can serve things directly from the buckets.    They would also like delete privileges."
Answer: 348.0

User story: "Looking at the recent log from the failed 300 visit jointcal run by [~<USER>, I noticed that I don't appear to ever log the total number of MeasuredStars in jointcal. This is an important number to help estimate memory pressure.    It's probably simplest to count and log it at the end of {{Associations::selectFittedStars()}}."
Answer: 8121.0

User story: "Add a cron job that will download the validation data to a known location. This location will be {{/project/shared/data/[testdata|validation_data]}} for now. I am using the {{lsstsw}} user to do the downloading so that we can make sure people are not inadvertently changing the branch etc.    Datasets will be:   {{validation_data_hsc}}   {{validation_data_decam}}   {{validation_data_cfht}}   {{testdata_jointcal}}   {{testdata_cfht}}   {{testdata_subaru}}   {{testdata_decam}}   {{ap_verify_testdata}}   {{ap_pipe_testdata}}   {{ci_hsc}}   {{afwdata}}"
Answer: 7191.0

User story: "Update shebang in python executables to point to python3"
Answer: 12891.0

User story: "Update shebang in python executables to point to python3"
Answer: 12885.0

User story: "Update logging on ATHS to be directed to a file in addition that to the scree."
Answer: 57685.0

User story: "LPM-251 should be completed by the next AMCL meeting (~August 2019)"
Answer: 642613.0

User story: "Time spent going to Labview training. "
Answer: 20676.0

User story: "Aerosol attenuation as a function of wavelength is described in the following way :    _attenuation(lambda) = AOD * lambda **(-a)_    Where _a_ is called the angstrom exponent.  I was only discussing AOD in the paper, but I could also show angstrom exponent, although there are only 2-D data available.  -> I am downloading 2-D angstrom exponent for both sites."
Answer: 285186.0

User story: " The paper \title\{Local monitoring of atmopsheric transparency from the NASA MERRA-2 global assimilation system} https://www.overleaf.com/read/yryfbzrdryhm    Is assessing the usefulness of earth monitoring satellites for astronomical purpose.  One of the finding is that the more a given component is mostly in the upper atmosphere, the better its variability is captured by satellites. As a clear illustration, I shall add profiles of all aerosols species in Appendix."
Answer: 285190.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 paper \title\{Local monitoring of atmopsheric transparency from the NASA MERRA-2 global assimilation system} https://www.overleaf.com/read/yryfbzrdryhm  Is assessing the usefulness of earth monitoring satellites for astronomical purpose.  One of the finding is that the more a given component is mostly in the upper atmosphere, the better its variability is captured by satellites. As a clear illustration, I shall add profiles of all aerosols species in Appendix.    "
Answer: 18712.0

User story: "The performance of using Firefly to visualize data in Jupyter notebook is very different between accessing lsst-demo, and accessing lsp-int.     The SUIT team has been trying to isolate the issue for quite a while.     We had a breakthrough couple of weeks ago and created  https://jira.lsstcorp.org/browse/IHS-2014.     We have been putting comments in IHS-2014 to document the work and findings.     "
Answer: 25046.0

User story: "DM-9873 added support for {{None}} to be added to PropertyList. Update afw FITS reading to support undefined values."
Answer: 1417.0

User story: "Changes to daf_butler introduced some behavior that cause sqlalchemy deprecation warnings to be thrown. This ticket will find out why they are being thrown and attempt to fix our code or prevent the warnings from being thrown."
Answer: 63.0

User story: "pyvo.describe throws an exception, so when you run:       {code:python}  import pyvo    service = pyvo.dal.TAPService('https://lsst-lsp-stable.ncsa.illinois.edu/api/tap')  service.describe()  {code}    Throws this:    {code}  TypeError: homogeneous list must contain only objects of type '<class 'pyvo.io.vosi.voresource.SecurityMethod'>'  {code}       It looks like it is choking on the security method parts of the capabilities file, but I'm not exactly sure why yet."
Answer: 22239.0

User story: "Write first draft of test scripts for acceptance test cases"
Answer: 222399.0

User story: "In the cases where a test case in LDM-639 is covered by one or more test cases in lower level test specifications, the high level test activity may be just an inspection. Detailed high level test cases are required if an LSE-61 requirement is not decomposed into lower-level component requirements."
Answer: 222428.0

User story: "In working on DM-9873 I was getting confusing test failures because sometimes a pex_exceptions C++ TypeError was turning up in Python as a RuntimeError.  It transpires that DM-9435 changed the C++ side such that TypeError inherits from LogicError but did not change the Python interface wrapper.  This ticket will change the Python side to inherit from LogicError rather than RuntimeError."
Answer: 369.0

User story: "Specify the configuration and price the phase 2 EFD servers, then   create a requisition for their purchase. Separately spec the add-ons  (nVME, SSD, HD)"
Answer: 22055.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: "Decide what kind of simulations may be helpful for checking out a wavefront-based PSF model for HSC.  Probably same variation on running batoid, with chip displacements and tilts, and adding an atmosphere of some sort on top.  We'd need to decide what kind of exposure-to-exposure variations would be useful to insert.  Also, do we want full images or just cutouts?  or maybe just wavefronts in some cases?    A stretch goal may be to also simulate donut exposures so we can mimic the entire loop of    • donuts -> active degrees of freedom    • in focus -> PSF model constraints -> residuals    though maybe there's a good way to skip that part."
Answer: 234142.0

User story: "MTDome SW Planning Meetings at Vendor Site (EIE-Italy)"
Answer: 20827.0

User story: "MTDome SW Planning Meetings at Vendor Site (EIE-Italy)"
Answer: 40683.0

User story: "Try extracting a PixelScaleBoundedField object from some joint cal runs.  Use that to develop a polynomial model for HSC distortion that can be used when fitting donuts."
Answer: 115714.0

User story: "Build the EFD writers against SAL 3.9 and deploy to a test machine on the pLAN  cluster to evaluate compatibility issues"
Answer: 61263.0

User story: "Install  and test the EFD writers for Influxdb built against the latest OpenSplice"
Answer: 19118.0

User story: "Test the performance of writing the EFD data to the Kafka brokers  provided by the DM test setup, use the M1M3 simulator to generate the maximum  data rate"
Answer: 61270.0

User story: "In working with oracle, exceptions were being thrown related to connections not being closed properly, leading to the addition of the __del__ method in the butler to make sure the connections were properly cleaned up in registry held by the butler.    This however had the side effect of creating an exception when a butler was used in a single threaded way. The temporary solution to that was to add an explicit close method to the butler to make sure everything was finalized before garbage collection (as __del__ is not predicable in the timing or ordering when it is evoked.    This ticket will explore why this is all necessary, and address what is causing the unexpected behavior. "
Answer: 1108.0

User story: "The butlerRoot change missed a file in the Oracle registry, this fixes that."
Answer: 865.0

User story: "• oauth2_proxy PRs to upstream need to be updated  • Test cases need to be added for JWT authorizer  • Kubernetes configurations need to be cleaned up for  -  oauth2_proxy   - jwt_authorizer   -  .well-known/jwks.json nginx container    - redis backend for oauth2_proxy and jwt_authorizer  "
Answer: 121234.0

User story: "DMTN-094 needs to be modified to reflect some new understandings we have when implementing the auth system"
Answer: 2495.0

User story: "Write up an implementation note of the auth system. Cover the following components:    oauth2_proxy  jwt_authorizer  kubernetes  CILogon  Token Issuance  "
Answer: 121238.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 full ci_hsc in Gen3 using weekly software release and Pegasus. Use Oracle backend if possible, otherwise sqlite3. Report any issues to appropriate dev teams.  "
Answer: 40433.0

User story: "Run full ci_hsc in Gen3 using weekly software release and Pegasus. Use Oracle backend if possible, otherwise sqlite3. Report any issues to appropriate dev teams.  "
Answer: 40434.0

User story: "Create a Gen3 Butler repo containing HSC-RC2 data (raw, calib, refcat..) based on Oracle registry.    The goal is to do Gen3 ingestion if possible.  Otherwise, bootstrap the Gen3 repo from Gen2 repos (gen2convert)."
Answer: 101092.0

User story: "As part of our desire to have regular ~monthly processing of HiTS, we'd like to generate templates.  Meredith reports this is more time-consuming than it could be.  This ticket is to write a script to automate this to the extent possible"
Answer: 399473.0

User story: "Run full ci_hsc in Gen3 using weekly software release, Pegasus, and sqlite3 as butler backend.    Report any issues to appropriate dev teams.    "
Answer: 16279.0

User story: "Run full ci_hsc in Gen3 using weekly software release, Pegasus, and sqlite3 as butler backend.    Report any issues to appropriate dev teams.  "
Answer: 1341.0

User story: "Similar to DM-18176 but for April 2019.    Currently, the gen3.sqlite3 output of the Gen2 ci_hsc run is needed to bootstrap running in Gen3.    Run ci_hsc with the weekly software releases.  Give gen3.sqlite3 file to database admins for loading into Oracle.  "
Answer: 40483.0

User story: "The mojave builds are failing with the following error:  {quote}  + pip install virtualenv  /Users/square/j/ws/release/tarball/osx/10.9/clang-1000.10.44.4/miniconda3-4.5.12-1172c30_tmp/durable-67d1fe51/script.sh: line 3: pip: command not found  script returned exit code 127  {quote}    An example failing build is [here|https://ci.lsst.codes/blue/organizations/jenkins/release%2Ftarball/detail/tarball/4040/pipeline/].  Which is calling code [here|https://github.com/lsst-sqre/jenkins-dm-jobs/blob/fd5ab2e1c2b73eb8ec08550bf7e9bcfa125154a3/pipelines/release/tarball.groovy#L610]"
Answer: 1306.0

User story: "Currently the only monitoring and status available is via pegasus-status (or condor_q).  All of the pipeline steps run pipetask as the executable, so pegasus-status does not help an operator to figure out much other than how many are running or have been completed.   Either figure out a way to annotate things so that pegasus-status provides better information or provide python code to be used."
Answer: 86933.0

User story: "Create sets of simulated images that have variable seeing, but with everything else the same between each set. The range of seeing should increase between each set, starting with a very narrow range and increasing by ~10% between sets.     These simulations are needed to quantify the impact of including higher seeing observations on the DCR model algorithm."
Answer: 5760.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 test transfer approach for a campaign of processing outputs to examine issues that may be encountered in such transfer from CC-IN2P3 to NCSA. We observe the significance of using "pipes/tar" versus naively performing a recursive copy for a directory spaces with a large number of directories and files (potentially small files).
Answer: 3.0

User story: "RFC-588   was approved at the DM-CCB, the changes need to be implemented in MagicDraw"
Answer: 163.0

User story: "The nightly failed because macOS mojave does not interact well with the JSON loading test of validate_drp.  Some of the plotting tests result in a segv with the TkAgg matplotlib backend (some strange interaction with tkinter and macOS).  The fix is to add {{~/matplotlib/matplotlibrc}} to the worker nodes and have a line in that file saying {{backend : Agg}}."
Answer: 1441.0

User story: "Using Tiago's docker container method, deploy key Auxiliary Telescope simulator containers down in lab. "
Answer: 61099.0

User story: "We organize a minimal Rucio install/setup with the latest release as the framework to implement first prototype features, such as registering files in place, investigating Oracle database integration, etc. 'Minimal' conveys that the setup at first will not have any of the numerous Rucio daemons configured and running, but will have the API available through https, with a database integrated (MariaDB to start). With this setup it will be possible to define RSEs (Rucio Storage Element's) and upload or add replicas to Rucio."
Answer: 4.0

User story: "The new jointcal and obs_lsst functionality was great this past week. It was like you built us a bunch of toys and then let me be the first to play with them.  (Will show you tomorrow). Only thing I've noticed is missing:     Three configs for jointcal or processCcd reruns:    Declination diff all looks very different as it should for 3 reruns:  https://lsst-web.ncsa.illinois.edu/~<USER>QA_DC2/processCcd/i/tract-3633/visit-204706/plot-v204706-matches_dec-psfMagHist.png  https://lsst-web.ncsa.illinois.edu/~<USER>QA_DC2/jointcal_default/i/tract-3633/visit-204706/plot-v204706-matches_dec-psfMagHist.png  https://lsst-web.ncsa.illinois.edu/~<USER>QA_DC2/jointcal_simple_3_1mas/i/tract-3633/visit-204706/plot-v204706-matches_dec-psfMagHist.png    But distance all looks the same.   From same runs of visit analysis (behold timestamps). Repos are clean.     https://lsst-web.ncsa.illinois.edu/~<USER>QA_DC2/processCcd/i/tract-3633/visit-204706/plot-v204706-matches_distance-psfMagHist.png  https://lsst-web.ncsa.illinois.edu/~<USER>QA_DC2/jointcal_default/i/tract-3633/visit-204706/plot-v204706-matches_distance-psfMagHist.png  https://lsst-web.ncsa.illinois.edu/~<USER>QA_DC2/jointcal_simple_3_1mas/i/tract-3633/visit-204706/plot-v204706-matches_distance-psfMagHist.png    I don't really know how this would be possible, except that they're not using jointcal.       "
Answer: 102156.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: "Write my portion of presentation on the LSST deblender for the April 1st DESC Blending Task Force meeting. This will describe the work to use a new normalization scheme, choosing the proper PSF model, issues with PSF convolution in HSC and (likely) LSST, and the new architecture."
Answer: 33721.0

User story: "The current implementation of the iterative forward modeling algorithm used to construct a DCR model appears to suppress differences between the subfilter model planes. This is currently overcome by running many iterations of modeling, which eventually recovers the missing frequency structure. While working on DM-17528 I developed code that overcomes this suppression and speeds up convergence by an order of magnitude, but it is not fully verified. This ticket is to rigorously develop and test that preliminary code."
Answer: 47832.0

User story: "Following my November 2018 trip to Princeton, draw up a “block schedule” of when we expect to be working on the various LDM-151 derived work packages.    This is useful for pipelines scheduling, but is also essential input to ORR planning [~<USER>; as such, it should be done (at least in initial form) by end-April 2019.    Note that of course the schedule will continue to evolve in response to changing priorities and emergent needs: we have seen over the last ~2 years that the DM replan schedule was rapidly rendered obsolete in many respects. As such, we regard this as a starting point for discussion rather than a commitment to specific delivery dates."
Answer: 374848.0

User story: "I took an action at the most recent DMLT to work with [~<USER> to sanitize the obs packages based on current best practices and gen3 considerations.  This is intended to start April 15 and be time boxed at two weeks.    The intent of this first part will be to separate calibration like data from the configuration and code aspects of obs packages.  Default information for some calibrations may be allowed, but it should be ingested into a formal calibration registry at scons time.    {{obs_subaru}} was chosen as the example to start with since it contains defects for multiple epochs in a format close to the one we expect to be the standard already."
Answer: 121274.0

User story: "Please remove Jenkins pipeline dax/docker/build-release, which hasn't been run in over 10 months, is no longer needed, and could never work again in any case :-)"
Answer: 8796.0

User story: "Configure MariaDB + efdwriters and Influx + efdwriters in La Serena and run MTM1M3 simulator for testing "
Answer: 29004.0

User story: "Do the research of InfluxDB and Kafka and learn how to use them. This is based on the discussion of EFD meeting:    [https://confluence.lsstcorp.org/pages/viewpage.action?spaceKey=LTS&title=2019-03-29+EFD+Meeting+notes]     "
Answer: 20735.0

User story: "Use the yaml configuration file format phase 1. This task will use the yaml to manage the configuration files. This task is the phase 1."
Answer: 17445.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: "Update the WEP package to use the eups package manager. This is to fulfill the requirement of LTS-186 to put the WEP into the scientific pipeline. The OFC is using the eups now. This task will need to fix the pep-8 syntax error by flake8 and follow the naming convention of test script. This task will also add the package dependency to the eups configuration file. This task may also need to fix the bugs for the new version of scientific pipeline and phosim_utils. The previous scientific pipeline used in WEP is w_2019_02."
Answer: 17430.0

User story: "This ticket is to gather minor updates to LDM-612 and LDM-682."
Answer: 15938.0

User story: "Qserv container builds seem to be now picking up binary tarballs, which is causing a shebang lossage with {{pytest}} when {{eups distrib}} tries to build the {{db}} package.    Proposed fix is to first install {{pytest}}, then run {{shebangatron}}, then install {{qserv}}."
Answer: 122.0

User story: "Got DESC DC2 7-visit i-band of the Run2.1i data from Jim at {{/scratch/<USER>DC2/Run2.1i/output}} and raw files at {{/scratch/<USER>DC2/Run2.1i/Run2.1i_raw_files/}}. Stored a copy at /datasets/dc2/         The ref_cats is the most recent, but the up-to-date CALIB products are not yet available and this was the Run1.2i versions. The tract ID is 3633.      "
Answer: 6.0

User story: "FibreSpectrograph Lab testing"
Answer: 468593.0

User story: "Life at NCSA will be simpler if the JupyterHub container doesn't start as root either."
Answer: 144.0

User story: "FIbreSpectrograph Code port from LabView to Python-part 2"
Answer: 230936.0

User story: "FIbreSpectrograph Code port from LabView to Python-part 1"
Answer: 149124.0

User story: "Based on the results of DM-17528, quantify the average number of additional false detections as a function of the range of seeing going into the templates."
Answer: 45157.0

User story: "There have been reports of some issues with ingest of BOT flat field data. [~<USER> has given me a file to use for the investigation."
Answer: 7285.0

User story: "DM-15597 analyzed fits to COSMOS galaxies using MultiProFit. Since then, DM-18105, DM-18515 and DM-18585 have added new features, so the fits and analysis thereof need to be updated."
Answer: 98570.0

User story: At present, there is automated workspace cleanup based on a free space threshold.  This doesn't solve the case of forcing a mass cleanup when the workspace(s) for a job have corrupted state. Previously, an option to force a cleanup was provided on several jobs. However, this would only cleanup the workspace(s) in which the triggered build would be running and not all workspace(s) associated with that job.  A mechanism is clearly need to allow either all workspace(s) for all jobs to be cleaned up as the "nuclear option" or to allow all of the workspace(s) for a signal job to be purged.
Answer: 8681.0

User story: "BVan would like to play with the credential store."
Answer: 88408.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 merging the new conda environment, the dev guide needs to be updated in order to document that the python version baselined is now 3.7"
Answer: 7118.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: Environment update to Python 3.7 seems to have busted the scisql build.  The problem seems to be an incompato in the "waf" build too used by scisql.  The waf project has already implemented a fix; this needs to be tested with scisql and upstreamed there if it addresses the build issue.
Answer: 140.0

User story: "On DM-17536, [~<USER> established that correlated variation in lightcurves from AP was due to the photometric calibration of “steady” sources in single frame processing varying from visit to visit. Figure out what's going on!"
Answer: 58230.0

User story: "If practical, please have {{getCurrentTime}} return TAI even if there is no time server. I suggest doing this by assuming the system clock is keeping good UTC and adding the appropriate number of leap seconds.    This would require a leap second table, preferably a data file so we don't have to recompile code if and when a leap second is announced.    If the way SAL reports TAI when it has a time server is to assume that the time server is keeping TAI (even though most of them keep UTC) then this suggestion may not be practical."
Answer: 360602.0

User story: SAL getCurrentTime will return the system clock (which is typically UTC) if it cannot find a time server. It will return TAI if it can see a time server and that time server is running TAI.    Please add the ability to query information about the time ("time metadata"). Any of the following information that is available would be appreciated:  * Named IP address or other identification of the time server, or an empty string if not listening to a time server. (E.g. "tai.lsst.noao")  * Is the time TAI or UTC? Please only offer this if SAL has a trivial, reliable way to know this, e.g. if the time server reports this to SAL. Trying to work it out by comparing the system clock to the time server is too complicated and error prone.  * Quality metrics, if any are available, such as stability, quality of connection to the time server...    I would strongly prefer that this metadata be made available via a new function or functions. The existing {{getCurrentTime}} is great as it is and it is widely used. I see no point to changing it and breaking existing code.
Answer: 302738.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: "macOS Sierra compilers no longer build the stack with current python 3.7 conda env and need to be disabled until either their compilers are updated or the OS is updated.    {code}                  base: 17.0 :::::  [2019-03-28T15:42:32.618521Z] c++ -o tests/ptr tests/ptr.o -Llib/ -L/Users/square/j/ws/stack-os-matrix/osx.clang.py3/lsstsw/miniconda/envs/lsst-scipipe/lib/python3.7/config-3.7m-darwin/ -lbase  :::::  [2019-03-28T15:42:32.679134Z] running tests/testModuleImporter1... running tests/ptr... passed  :::::  [2019-03-28T15:42:32.695973Z] passed  :::::  [2019-03-28T15:42:32.723836Z] c++ -o python/_lsstcppimport.so -bundle -F/ -undefined suppress -flat_namespace -headerpad_max_install_names python/lsstcppimport.os -Llib/ -L/Users/square/j/ws/stack-os-matrix/osx.clang.py3/lsstsw/miniconda/envs/lsst-scipipe/lib/python3.7/config-3.7m-darwin/ -lbase -ldl -lpython3.7m  :::::  [2019-03-28T15:42:32.778592Z] ld: in /Users/square/j/ws/stack-os-matrix/osx.clang.py3/lsstsw/miniconda/envs/lsst-scipipe/lib/python3.7/config-3.7m-darwin//libpython3.7m.a(ceval.o), could not parse object file /Users/square/j/ws/stack-os-matrix/osx.clang.py3/lsstsw/miniconda/envs/lsst-scipipe/lib/python3.7/config-3.7m-darwin//libpython3.7m.a(ceval.o): 'Invalid record (Producer: 'LLVM4.0.1' Reader: 'LLVM APPLE_1_802.0.42_0')', using libLTO version 'LLVM version 8.1.0, (clang-802.0.42)' for architecture x86_64  :::::  [2019-03-28T15:42:32.779858Z] clang: error: linker command failed with exit code 1 (use -v to see invocation)  :::::  [2019-03-28T15:42:32.781368Z] scons: *** [python/_lsstcppimport.so] Error 1  :::::  [2019-03-28T15:42:33.341675Z] /Users/square/j/ws/stack-os-matrix/osx.clang.py3/lsstsw/build/base/doc/mainpage.dox:63: warning: unable to resolve link to `lsst.pipe.base.cmdLineTask.CmdLineTask' for \link command  :::::  [2019-03-28T15:42:33.536595Z] /Users/square/j/ws/stack-os-matrix/osx.clang.py3/lsstsw/build/base/doc/mainpage.dox:63: warning: unable to resolve link to `lsst.pipe.base.cmdLineTask.CmdLineTask' for \link command  :::::  [2019-03-28T15:42:35.216166Z] scons: building terminated because of errors.  ERROR (6 sec).  {code}"
Answer: 92.0

User story: "Clang version 10.0.1 (clang-1001.0.46.3) on macOS Mojave can not build boost 1.68.  v1.69 looks to have some fixes for the problem so we need to upgrade (Jenkins currently uses an older clang so may not have the problem since we know 1.68 builds fine with version 10.0.0 (clang-1000.10.44.4))."
Answer: 463.0

User story: "Test ATHexapod CSC fixes from at the summit. Fixed should be done in: https://jira.lsstcorp.org/browse/DM-18642"
Answer: 62507.0

User story:     Clean up Electrometer python code and add limits when applies (for example integration time should be limited). Also create a docker image for deployment.    Update:    * Configuration to use the API from salobj   * update intensity in events to "CurrentValue" or "Measurement" according to Patricks comments in [https://github.com/lsst-ts/ts_xml/pull/83#discussion-diff-279486587R15]
Answer: 122948.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: "     Improve Electrometer documentation inside python"
Answer: 67123.0

User story: "This task is to re-package electrometer to follow new standards and make it work with dm-stack (and Tiagos Docker image)."
Answer: 121838.0

User story: "When forwarder read out image pixels, it uses either ITL or E2V readout order. Currently, forwarder has hard-coded strings that should move out from code base and understand the differences among different test stands."
Answer: 162877.0

User story: "Once the new environment has been activated, the shared stack environment need to be updated accordingly."
Answer: 6942.0

User story: "Add ts_sal unit tests to test DM-18491 current time issues and DM-18637 get newest topic after get oldest does not always return the most recent value."
Answer: 12647.0

User story: "Develop a skeleton for the M1M3 thermal system software."
Answer: 21777.0

User story: Based on the API support for authentication tokens to be added to {{firefly_client}} under DM-18666, this ticket asks that {{display_firefly}} be modified to support both:  * manually supplying an authorization token for Firefly when the display object is created, and  * automatically picking up an appropriate token from a TBD mechanism in the Python process environment established by the Notebook Aspect (e.g., this may be from an environment variable with an agreed-upon name, or from a dot-file).    The second subtask requires, of course, that the "TBD mechanism" has been defined.  This will require work on the Notebook Aspect / Nublado as well.    In each case, the token should then be passed down to the underlying {{firefly_client}} object.    Care must be taken to be aware the different servers that might be used and to respect overrides that may be in place.  The "second subtask", it-just-works, method is initially only required to work for whatever the active LSP-instance default Firefly server is (including any system-configured overrides to that).  If the _user_ wishes to use a different server, s/he may be required to supply an appropriate token manually.
Answer: 190364.0

User story: Please add an interface to {{firefly_client}} for supplying authorization headers to be added to the requests and uploads transmitted to the Firefly server.    At first this should just be an API for "manually" supplying a token obtained elsewhere.    At a later date it may be appropriate to have an option for {{firefly_client}} to pick up a token, if available, from the environment in which it is running, e.g., from an environment variable or a dot-file, but that decision is yet to be taken.    For now the token, for use in the LSST environment, will be obtained from the API Aspect's Get-Token web page, as recently prototyped by [~<USER>.
Answer: 163178.0

User story: "Logically arrange the 6 Oracle nodes into 3 nodes for development and testing, and 3 nodes for pre-production."
Answer: 9912.0

User story: "Develop process by which users acquire new Oracle accounts, including Oracle wallet setup."
Answer: 9916.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: "Modify initial Oracle configuration and storage architecture to suit the needs of Gen3 Butler."
Answer: 9919.0

User story: "Upgrade Oracle Trace File Analyzer, used for analysis and problem resolution."
Answer: 9921.0

User story: "Develop integration plan between Oracle install and configuration process, and Puppet processes owned by sysadmins."
Answer: 9922.0

User story: "After a grace period of a few business days, duplicate jobs need to be removed to prevent duplicate builds."
Answer: 421122.0

User story: "    Improve Electrometer documentation in the XML"
Answer: 68011.0

User story: ts_sal develop commit c4c93b81 March 27, 2019 at 9:25:29 AM fails when building the the Test SALPY library. The failure is in the "Generating Python SAL support for Test" phase:  {quote}  g++  -fPIC -g -m64 -Wno-write-strings -std=c++11 -D_REENTRANT -Wall -I"." -I"/opt/OpenSpliceDDS/V6.9/HDE/x86_64.linux/examples/include" -I"/opt/OpenSpliceDDS/V6.9/HDE/x86_64.linux/examples" -I"/opt/OpenSpliceDDS/V6.9/HDE/x86_64.linux/include" -I"/opt/OpenSpliceDDS/V6.9/HDE/x86_64.linux/include/sys" -I"/opt/OpenSpliceDDS/V6.9/HDE/x86_64.linux/include/dcps/C++/SACPP" -I"/opt/lsst/software/stack/python/miniconda3-4.5.4//include/python3.6m" -I"/home/saluser/tsrepos/ts_sal/lsstsal/include" -I"/opt/lsst/software/stack/python/miniconda3-4.5.4//include/python3.6m" -I../../../Test/cpp/src -I../../../Test/cpp -DSAL_BUILD_FOR_PYTHON -DSAL_SUBSYSTEM_ID_IS_KEYED -c  -o ".obj/SAL_Test_python.o" ../src/SAL_Test.cpp  ../src/SAL_Test.cpp: In constructor ‘SAL_Test::SAL_Test(int)’:  ../src/SAL_Test.cpp:19:7: error: ‘QosProvider’ was not declared in this scope         QosProvider qosProvider(qname,"DDS DefaultQosProfile");         ^~~~~~~~~~~  ../src/SAL_Test.cpp: In constructor ‘SAL_Test::SAL_Test()’:  ../src/SAL_Test.cpp:42:7: error: ‘QosProvider’ was not declared in this scope         QosProvider qosProvider(qname,"DDS DefaultQosProfile");         ^~~~~~~~~~~  {quote}
Answer: 2817.0

User story: "Modify current storage layout to incorporate new storage array, especially balancing workloads for maximum throughput and performance."
Answer: 10153.0

User story: Design test plan for new array, focusing especially on performance, and also initial "burn-in" to confirm stability..
Answer: 10154.0

User story: "Go over current hardware and operating system to determine any changes needed to support new storage array."
Answer: 10156.0

User story: "Spec servers needed to provide initial support for base database services."
Answer: 10162.0

User story: "Identify what base services need to interact with a relational database management system (RDBMS)."
Answer: 10167.0

User story: "At the moment there's no way for the user to determine, other than trial and error, what the environment limits are."
Answer: 3277.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: "Due to DM-18637 the timestamps in the ScriptQueue script event are not reliable (and a unit test sometimes fails because of this). If that bug issue cannot be fixed quickly then get sign-off on a workaround and apply it using this ticket branch."
Answer: 226.0

User story: "Fix ATHexapod bugs, this includes:   * Update motion detection to use in-built queries inside the PI controller properly  {color:#00875a}*(DONE by waiting until is ready for next command after doing any motion)*{color}   * Define pivot setup at the start properly. The pivot cannot be configure if the hexapod is in an angle, so trying to configure when starting if the hexapod was left with an angle different to 0, will fail the start command. Need to be discussed with Patrick. *{color:#00875a}(DONE by removing Pivot from settings){color}*   * Prior to executing command, check if the controller is ready to receive command, if not wait until ready (with a certain timeout)  *{color:#00875a}(DONE by waiting until is ready for next command after doing any motion){color}*   * Fix initialization, current initialization fails due that it takes some time to reference the hexapod at the start. If we don't initialize the Hexapod and there's no reference due to reference lost (lost of power), we won't be able to command it.Need to be discussed with Patrick. {color:#00875a} *(DONE by waiting until is ready for next command after doing any motion)*{color}"
Answer: 63939.0

User story: "MERRA-2 assimilation of ozone and PWV correlate with SNF estimates ([^merra2VSsnf.pdf] slides 2,3,4) while AOD does not ([^merra2VSsnf.pdf]slide 5).    Why is that ?    This will be discussed next week with Mauna Kea astronomers."
Answer: 20399.0

User story: "While going through the log files on Forwarder, it seems that Forwarder tried to continue executing the codes after not being able to fetch header file. At that point, it should halt and publish telemetry_status."
Answer: 17794.0

User story: "OCSBridge is not currently logging. Since Forwarder logging seems to be stable, we should integrate logging style from Forwarder to OCSBridge."
Answer: 34763.0

User story: "Running `matchedVisitMetrics`for DM-17830 was yielding AM1 of 0 for HSC WIDE tracts 9615 and 9697 which have visits numbers in the single digits. AM1 is the median of the RMS of the distances between 2 stars in N visits. Closer inspection revealed that more than half of the RMSs were exactly zero, which is why the median was exactly zero.  [~<USER> quickly found the problem which was that if a pair appeared in exactly one visit, the stdev([one distance]) was exactly 0  and not NaN.    Require at least 2 distances before computing their stdev.    [~<USER> will investigate the potential bias is in the median RMS as a function of N.    This change will increase our reported AMx reported in squash."
Answer: 3953.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 Ops rehearsal is described at: LDM-643.lsst.io Current estimate for this rehearsal is between 29 Apr 29 17 May 2019. The goal is to simulate 2-3 days of operations. "
Answer: 69593.0

User story: DESC reported that running jointcal on Run2.1i did not improve the photometric repeatability (esp. wrt the reference catalog) relative to processCcd.  This is not surprising because:  1) The reference catalogs are near perfect and to full depth < 23.  They essentially are the input catalogs, and therefore jointcal's benefit of bootstrapping deeper stars is not realized.  2) There is no vignetting or sub-ccd throughput variability in the imsim images in Run2.1i.  Therefore, the photoCalTask model of "1 zeropoint per ccd" is the correct model, and jointcal's ability to have variable throughput across the focal plane and per ccd is not needed.    However, various test plots (either via [~<USER> or the {{visitAnalysis}} scripts) show that the calibrated photometry is only consistent with the reference catalogs at the 13-16 mmag level, which is _much_ larger than I would expect for clean simulated data for bright stars (basically, I would expect few mmag consistency).    This ticket is to describe work to see where in processCcd/jointcal things are going wrong.  
Answer: 1175.0

User story: "[DMTN-006|https://dmtn-006.lsst.io] & DMTN-021 describe an investigation into image differencing with the DM codebase that (superficially, at least) seems to provide cleaner results than our modern application of ip_diffim. What's changed? Can we reproduce the old results?    Start by chatting to <USER>to see if any of the DMTN-006 / DMTN-021 configuration is still available. See if there are major changes between that and the modern defaults which could explain any differences.    Evaluate how practical it is to reproduce DMTN-006 / DMTN-021 based on the modern codebase (many things have changed in the three years since that document was written, so it's not clear how much effort that might involve). Don't actually do that reproduction on this ticket, though — if it seems doable, make another ticket to describe that work."
Answer: 45158.0

User story: "Sometimes, it can be convenient to compare diffims generated from the same data by two different pipeline runs (e.g. with different versions of the code, different configurations, etc). Write some scripts to make this convenient.    These initial scripts don't need to be polished or high-quality “engineering grade” — we'll regard this as an exploratory exercise and see how useful this approach is before we decide to devote significant effort to it in future."
Answer: 163396.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: "DESC reported that running jointcal on Run2.1i made the astrometry repeatability worse than processCcd.  This is not surprising because:    1) The reference catalogs are near perfect and to full depth < 23.  They essentially are the input catalogs, and therefor  jointcal's benefit of bootstrapping deeper is not realized.     2) ProcessCcd fits a 3rd order polynomial per-ccd. Jointcal is fitting a model that is 1st order per ccd and 7th order per focal plane. The jointcal model is more robust, but doesn't have as many degrees of freedom as the processCcd model.     [~<USER> copied over a tract to lsst-dev for us to play with. Thanks to [~<USER> for ingesting it and running it through singleFrame processing. On this ticket, I'll post the results of:    1) Running {{validateDrp}} and {{visitAnalysis}} on 4 different config repos:    2) Reconciling metrics posted in validateDrp and visitAnalysis from the ones computed in Jim's notebook    3) Rerunning single frame using only bright stars from the reference catalog. "
Answer: 44523.0

User story: "Gaussian process has been successfully applied to a subset (about ~500 data points) of MERRA-2 monitoring (see [^gaussian_process.pdf]).     Gaussian process determination is too slow to. be applied to the entire timeline (24 h *365 days*8 years = 70 000.)    An other approach has to be explored :    - rebinning?    - autocorrelation to determine the hyperparameters of the gaussian process ?     "
Answer: 18943.0

User story: Contribute to the document "Release Scenarios for LSST Data" [https://lso-011.lsst.io|https://lso-011.lsst.io/] 
Answer: 333648.0

User story: "With Schema pickleable (DM-17950), I can now use ProcessPools to parallelize reading data. But pickle/unpickle of SourceCatalogs seems to be preventing that from actually providing a speed boost. I've found at least one obvious place to gain a big chunk of speed. I'll spend a little more time looking for others."
Answer: 34554.0

User story: "The T&S group would like to publish artifacts directly to a pair of S3 buckets attached to their account.  The buckets should be created and should be named:    SAL_Objects – for the binary products of the build process    SAL_Topic_Registry – for static pages (I believe)    They will also need a user who has the ability to administer the S3 buckets and a token for access."
Answer: 11207.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 `constructDark.py` on an auxtel dark (2019030800135, see below), the following error appears:          lsst::pex::exceptions::LengthError: 'Too many CR pixels (max 500000)'         Visual inspection of     "AT_O_20190308_000135-ats-wfs_ccd.fits" (see directory below) shows that there are not as many CR's.    -Data (see IMGTYPE in headers for types, which follows the entry in [https://confluence.lsstcorp.org/pages/viewpage.action?spaceKey=SYSENG&title=LogBook+for+AuxTel+camera+diagnostic+data+taking] under MAR08, 2019):     /project/<USER>data/auxtel_DMCS_images_2019-03-08/cal    -ID:     WARN: Unable to process DataId(initialdata=\{'imageType': 'DARK', 'dayObs': '2019-03-08', 'visit': 2019030800135, 'detector': 0, 'detectorName': 'S00'}    -Command run:    * constructDark.py /project/<USER>calibrations_auxtel_mar20_REPO --calib /project/<USER>calibrations_auxtel_mar20_CALIB/ --output /project/<USER>calibrations_auxtel_mar20_OUTPUT/ --id imageType='DARK' --batch-type none --clobber-config    stack: "w_2019_11" with branch "tickets/DM-18051" of "obs_lsst"
Answer: 3960.0

User story: "[https://jenkins.io/security/advisory/2019-03-25/]"
Answer: 4694.0

User story: "[https://jenkins.io/security/advisory/2019-03-25/]"
Answer: 3276.0

User story: "Draft VCD for DM"
Answer: 124341.0

User story: "This task covers the time needed to update LSE-229.  It is a draft document covering the middleware communication design."
Answer: 113000.0

User story: "Add additional functionality to cameraGeom to reflect use cases identified in obs_lsst, while bringing obs_lsst usage in line with the intent of the cameraGeom design.  This includes:   * Add additional amplifier/detector fields for flips in pre-raw to raw transmission.   * Add accessor to get (computed) raw readout corner.   * Rename methods that always reflect assembled state to make this explicit in the names; deprecate the old names.   * Add new fields that track the trim/assembly state.   * Add new accessors for bounding boxes and readout corner that utilize trim/assembly state.   * Add setters for all fields, along with runtime freezing: only frozen Detectors can be added to an Exposure, but an unfrozen Detector can be obtained by copying a frozen Detector.    At least some of these changes are API changes and will need an RFC.  I'd like to prototype them out on this ticket branch first."
Answer: 323126.0

User story: "Update LSE-319 for the LSP Review, notably including clarification of the set of IVOA standards that are relevant."
Answer: 247878.0

User story: "Migrate the cookiecutter templates for creating reStructuredText technotes into [https://github.com/lsst/templates] so that they can become available through templatekit and SQuaRE Bot on Slack:   - [https://github.com/lsst-sqre/lsst-technote-bootstrap] (reStructuredText)"
Answer: 56949.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> will soon be testing ATDome against the vendor's TCP/IP interface and bugs are bound to show up. This ticket is to capture the bugs and provide a ticket branch on which to fix them.    Also add the TCP/IP host address (when chosen) and port=17310"
Answer: 34630.0