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: "When testing adding reference stars to fgcmcal, use the HSC S18a dataset to check that things are working and investigate questions of color terms / signal-to-noise / etc from the PS1 reference catalog.  Furthermore, this exercises the cross-calibration of the HSC r/r2 and i/i2 filters, and further checks for bimodality issues in the solution as first uncovered in DM-15895.     "
Answer: 141613.0

User story: "When testing adding reference stars to fgcmcal, use the RC2 dataset to check that things are working and investigate questions of color terms / signal-to-noise / etc from the PS1 reference catalog."
Answer: 141615.0

User story: "The fgcm fitter needs to be modified to take into account reference stars.  This ticket summarizes the work on the math to compute the updated chi2 and derivative of the chi2."
Answer: 6.0

User story: "- Update the milestones repository with data extracted from PMCS (/)  - Update LDM-503, LDM-564, images repository (/)  - Update milestone dates loaded into Jira (/)  - Update skeleton Feb 2019 monthly report (/)  - Circulate upcoming milestone list to dm-cams (/)  - Audit and update https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests (/)"
Answer: 443.0

User story: "include similar aspects as found in the WLCG MOU annex #3 as appropriate for LSST in the ODF."
Answer: 24487.0

User story: We have two beefy "machines" in Google cloud for our tests (ppdb-test-server and ppdb-test-client), need to install all software that is necessary for the tests:   * for client I just need lsst stack with dax_ppdb in it, plus the database backend driver for potgres (I think I used psycopg2 at in2p3)   * for server we need more or less recent version (10?) of Postgres installed from RPMs, properly configured
Answer: 1334.0

User story: "It'd be nice to have the ability to display tokens after creation, and the ability to delete all secrets under a path with revocation of the tokens."
Answer: 29.0

User story: "cmake-based dependents of the libcurl eups component fail under ubuntu with    {{libcurl/7.53.1/lib/libcurl.so.4: no version information available (required by /usr/bin/cmake)}}    It looks like an additional configure option is needed in the eupspkg.sh script to get the library built with the appropriate version information (cribbed from the debian package script for libcurl)"
Answer: 339.0

User story: "Attempt to use the SDM-system to create Pandas DataFrame catalogs that look similar to, and have the same values as, the outputs of the current DPDDifier.    This can just a proof-of-concept in a notebook, or similar."
Answer: 23059.0

User story: "Use the new lsstvaultutils tools to get a current copy of Jellybean secrets into Vault, and then document how to use them to maintain the secrets."
Answer: 1448.0

User story: "The current monochromator CSC, currently written in LabView, has an issue that we are unable to solve. I will re-write it using salobj. "
Answer: 13455.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: "request_script.py is a utility script to interact with the queue. It was written some time ago with an old version of sal and when I did not have a clear idea where to put it. I will re-write the script using the newest version of SAL and will put in in ts_scriptqueue.    =============================================    The ui module contains two submodules; a model interface and a command line front end. The model hosts a global ui for the script queue and the front end provides the interface to interact with it (both input and output).    For the front end I'm using a the python cmd standard library, with the possibility to extend it to use cmd2. This gives user some nice capabilities like auto complete and helper. functions. One of the main issues with that library is that it is not asyncio friendly, so I had to do some workaround and rely on SAL to store the information until the user request it. The idea of having the process running all the time and rely on cmd is to recycle the remote to talk to the queue. The previous version was really slow since you had to subscribe to the remote every time you run the script.    I think this script will probably be a useful utility at early stages of interacting with the queue. I did not included tests for the ui modules. I think this could be a good addition for a next release, but I could also think about some simple tests to perform.    Also, updates timeouts for the script queue.     "
Answer: 13462.0

User story: "Our current options for a new persistence framework are Cereal, FlatBuffer, and/or Avro. I've already looked into Cereal and FlatBuffer; examine the suitability of Avro for the same work."
Answer: 21668.0

User story: "Instead of hard-coding the contained classes, reimplement {{ExposureInfo}} using a type-safe heterogeneous map. The existing interface should be left as-is (or, at most, deprecated). This ticket does not include migrating {{ExposureInfo}} away from {{afw::table::io}} persistence."
Answer: 246421.0

User story: "As discussed on [CLO|https://community.lsst.org/t/3384], a type-safe heterogenous map in C++ would make it easier to decouple classes that logically contain each other. Design and implement a map interface, as well as one concrete implementation."
Answer: 112867.0

User story: "Create a Helm chart repository and give instructions on how to use it. This is meant to be a place where we can store the Helm charts created by SQuaRE, package and share them.     There are several options for hosting the chart repo, see https://github.com/helm/helm/blob/master/docs/chart_repository.md"
Answer: 1559.0

User story: "If the header card being used to generate {{visit_id}} is a string, it can end up as a {{str}} in the {{ObservationInfo}}. [^test_hdr.txt] "
Answer: 449.0

User story: "Continue SAL++ mentoring"
Answer: 14535.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: "Backup all the EFD data collected during the M1M3 test campaigns at the mirror lab.    Retrieve the EDF machine and integrate back into the simulation cluster.    Copy data to NCSA if a destination location is provided"
Answer: 59019.0

User story: "Change the implementation of SAL hash codes to include control over topic names as well as DDS types. This should avoid namespace collisions when CSC XML is updated"
Answer: 40344.0

User story: "Please document, and note in this ticket where it's documented, all URLs currently in use in any Firefly application that is in use or planned to be in use in LSST (default data portal, slate, time series viewer, etc.).    Before our closeout I want to be sure that we have a coherently laid out scheme for these."
Answer: 145923.0

User story: "Install Labvier on my machine. and try to get the ts_sal Labview program running. I will be needing to run this for development. "
Answer: 3273.0

User story: "Get the newly created single file cpp scripts running on jenkins. This should improve speed at which the tests are ran. This because behind the scenes when your program does any interaction with DDS there is a lot of overhead. By having all the tests in a single program this overhead is started only once.    Hopefully we reduce the jenkins build time by using these test programs rather than running each individual program. "
Answer: 20201.0

User story: "The new URL is https://lsst-lsp-stable.ncsa.illinois.edu/"
Answer: 59.0

User story: "ATS system has been in idle state after December. This work captures the effort needed to run ATS system in Tucson."
Answer: 19118.0

User story: "Write a demo showing how to simulate fake sources  in the  tasks, including some background in how it works.  Test audience is the deblending task force on Feb 18th. Please attach slides. "
Answer: 4227.0

User story: "Draft a policy for including external code into data release production processing    This will be added to DMTN-106 to start a discussion at least.    Then perhaps something will go in LDM-294 or another controlled document."
Answer: 81134.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 is a small fix in our fork of {{cp-helm-charts}}. When I updated the "patch" version in DM-17531 I noticed the following in Tillers' logs:    {code}  [storage/driver] 2019/02/18 18:32:27 create: failed to create: ConfigMap "confluent.v1" is invalid: []: Too long: must have at most 1048576 characters  [tiller] 2019/02/18 18:32:27 warning: Failed to record release confluent: ConfigMap "confluent.v1" is invalid: []: Too long: must have at most 1048576 characters  [kube] 2019/02/18 18:32:27 building resources from manifest  [kube] 2019/02/18 18:32:27 creating 25 resource(s)  [tiller] 2019/02/18 18:32:28 executing 1 post-install hooks for confluent  [tiller] 2019/02/18 18:32:28 hooks complete for post-install confluent  [storage] 2019/02/18 18:32:28 updating release "confluent.v1"  [storage/driver] 2019/02/18 18:32:29 update: failed to update: configmaps "confluent.v1" not found  [tiller] 2019/02/18 18:32:29 warning: Failed to update release confluent: configmaps "confluent.v1" not found  [storage] 2019/02/18 18:32:34 getting last revision of "confluent"  {code}    The resources were correctly created and everything seemed to be deployed, but for the Terraform Helm provider and for Helm itself it was like the deployment failed because the {{cp-helm-charts}} release was not properly registered.     The ConfigMap "confluent.v1" was empty because the versions for the individual charts in {{cp-helm-charts}} also need to be updated.     It took me a while to find the root cause but the fix is small ;)  
Answer: 13.0

User story: "Before DM-17748 is completed it was deemed useful to test the efficiency and accuracy of different convolution and translation algorithms. This ticket documents that work, including investigating different algorithms, the creation of a diagnostics section to scarlet and a notebook that demonstrates the new algorithms which has been added to the {{torch}} directory in scarlet."
Answer: 40504.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: To get more information about the details of jointcal's fitting processes, we can output the "chi2 contributions" file at each stage of the {{_iterate_fit()}} "outer" python loop. This will provide some more details, without being too overwhelming. This would be a boolean config option (named {{writeChi2ContributionFilesOuter}}?) that defaults to False. The output files would follow the same naming convention as the initial/final ones, with the fit iteration appended.    This would also be a good time to clean up how {{saveChi2Contributions()}} generates the names of the files: we should pass some kind of format string to it and use a combination of {{find}} and {{replace}} in C++ to generate the two file names for the measured and reference stars. {{_iterate_fit()}} should also output a count for each iteration, so that we can more easily associate these new files with the outer fit loop log messages (which will have that count in their filename).    We need to decide whether to write the files before or after the fit loop: the current "initial_chi2" file is written immediately after the model is constructed, before any of the "initialization steps" are taken, while the "final" step happens after all fitting is complete.    Should this option also result in the "initialization steps" also being logged, or should the existing {{writeChi2ContributionFiles}} be modified to do that? The 3-4 initialization steps are by far the largest chi2 change, and have outlier rejection turned off, so they are both qualitatively and quantitatively different from the fit loop.
Answer: 62890.0

User story: "Many DM L2 milestones are dependent on delivery of functionality elsewhere in the project. However, this is not currently captured in the PMCS plan. Work with the other T/CAMs to determine external-to-DM prerequisites for DM L2 milestones, and, if necessary, with managers from other subsystems to make sure milestones capturing those prerequisites exist. Then ensure they are programmed into PMCS and captured in LDM-503."
Answer: 486799.0

User story: "Per discussion at the November 2018 DMLT F2F, we should refresh the list of DM L3 milestones. Each milestone should be tied directly to a DM deliverable (per the product tree), and hence should reflect delivery of specific DM services.    Work with the T/CAMs to refresh the DM milestone list appropriately."
Answer: 839395.0

User story: "Develop and support the active optics closed-loop simulation. This task will integrate the modules of ts_tcs_wep_phosim, ts_tcs_wep, and ts_tcs_ofcPython. This task will be a prototype of active optics closed-loop simulation. The prototype here will support the simulation of main telescope active optics system (MTAOS) in the final. This task is in the phase 3 of the development."
Answer: 17585.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: "Integrate the AOS closed-loop simulation with Jenkins server. I have the problem to let the Jenkins to get the repos existed in the docker image. This task will solve this problem and make sure the simulator can do the automatic unit tests on the Jenkins server."
Answer: 17587.0

User story: "In order to easily parallelize validate_drp's data loading, we need, at minimum, to be able to pickle/unpickle {{afw.table.Schema}} objects. This may or may not be made more difficult by the {{SchemaImpl}} design: I suspect a pybind11 master would have some ideas for how to do this relatively quickly.    Pickling support pybind11 docs for reference:  https://pybind11.readthedocs.io/en/stable/advanced/classes.html#pickling-support"
Answer: 29936.0

User story: "{{MultiBandDataIdContainer}} is not used anywhere and is duplicate of {{TractDataIdContainer}} in {{pipe/drivers/utils.py}}.   I suggest removing it to make the occasional debug less confusing."
Answer: 129.0

User story: "For the week of the 17th through the 21st, support Nick again.    We used scriptqueue to run a script which moved the one linear stage up a vertical track and then iterated the second linear stage on a horizontal track. The electrometer would then take data. The laser was propagating through fiber spectre cable that was inserted into the collimated beam projector. We got the electrometer managing to take data, with some small bugs along the way. The url that is returned does not actually return the ip address of the computer hosting the fits files. We tested Tiago's request_script.py which worked out pretty good except for some mildly annoying bugs but nothing breaking the scripts.    We also discovered that two electrometer CSCs can't be hosted on the same pc, at least as far as we tried. The manual did say that it had not been tested."
Answer: 19951.0

User story: "In order to get Jenkins to pass the unit tests, the Jenkinsfile needs to be changed because of some environment factors.     Started writing a dockerfile that contains all dependencies needed to run TunableLaser CSC as docker container. Have gotten through most of the setup with eups. Once the file is complete, upload to dockerhub and pull image in Jenkinsfile. "
Answer: 58901.0

User story: "When a user clicks on a button in an interaction message, SQuaRE Bot Jr needs to both recieve the POST from Slack corresponding to that message, and then also forward that message to a Kafka topic. See [https://api.slack.com/messaging/interactivity/enabling]    This is needed to enable the basic interactive messages created by templatebot in DM-17865."
Answer: 8810.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_10. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 38971.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

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

User story: "Run jointcal with HSC-RC2 and w_2019_10"
Answer: 35936.0

User story: "Representatives (M. Fisher-Levine, A. Plazas, A. Nomerotski, P. Antilogus, P. Astier) from DM and SAWG (DESC) had a telecon to discuss the topics to address during the joint DM-SAWG session at the next DESC winter meeting at Berkeley (2/27/19). The first topic will be a presentation from DM (by A. Plazas) on the state of the ISR, CPP pipelines (e.g., order of current ISR corrections, plan for generating calibration inputs, precision of current corrections, tests, etc).     This ticket will track the work on that, gathering input from DM people such as R. Lupton, C. Waters, and M. Fisher-Levine. "
Answer: 17232.0

User story: "* Follow up of focused DM-SAWG telecons (DM-17903, DM-17837, DM-17530)   * People present: M. Fisher-Levine, A. Plazas, A. Nomerotski (first 15 minutes), P. Astier, P. Antilogus    * Tentative points to discuss at DM-SAWG session in Berkeley (P. Antilogus will define the final agenda):    ** DM presentation (by [~<USER> with input from other DM people such as <USER> <USER> and Chris Waters) with current state of ISR and CPP pipelines   *** Order of ISR correction, precision of current corrections, tests   ** Provide examples of impacts on science (how well do we need to correct and why? Do we have enough information?):    *** Impacts on WL, PSF    *** Impact of CTI   *** Leave detailed discussion on BF out; it will have a dedicated SAWG session during the     ** How to use data from AuxTel?    * For the discussion we want to identify places that need work, tasks (e.g., algorithm validation, precision of corrections validation), priorities, and volunteers. "
Answer: 90.0

User story: "cmdLineFwk can read pre-built pipeline and quantum graph from pickle file, but it is not presently checking that object of correct type is read which can lead to exceptions in other places. Need to add simple check of the type of the object that was read."
Answer: 66409.0

User story: "This task covers the time spent to support M1M3 Mirror Lab testing."
Answer: 20464.0

User story: "Take Tiago's script that coordinates the monochromator, electrometer and fiber spectrograph to perform the steps needed when taking a flat field.    This script will serve as an example to future script composers."
Answer: 27318.0

User story: "It would be helpful to have easily interpretable plots for multi-band fitting showing all bands at once, rather than having to look at each band separately."
Answer: 20551.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: "Develpment of a model for main belt asteroid (MBA) population that serves as benchmark for the LSST asteroid discovery and data rate statistics requested by the MPC.    Asteroid orbits are drawn based on extrapolation of currently complete MBA populations as extracted from the MPC database."
Answer: 2.0

User story: "In order to provide the IAU Minor Planet Center with LSST data rates for solar system object discoveries and observations an efficient code is generated that can propagate a representative solar system model through LSST reference observation campains such as 2018b.           "
Answer: 38842.0

User story: "The automated tolerances computed in pessimistic B should never be smaller than the pixel scale. This ticket will resolve a bug discovered as part of looking into DM-17843 that allows that to be the case."
Answer: 1274.0

User story: "For DESC DC2 processing (at least!) there are reference catalogs that contain both unresolved (star) and resolved (galaxy) sources. For some purposes we want to be able to select out just the unresolved/stellar sources, and I imagine there could be other reference catalogs created in the future that are not pre-selected on stars.    Adding {{doUnresolved}} to the {{referenceSourceSelector}} can be done with ~5 lines of code + copying the appropriate test from {{ScienceSourceSelectorTaskTest}}."
Answer: 1138.0

User story: "Using a bleed version of the conda environment, afw test case PhotoCalibTestCase fails with the following error:         > self.assertEqual(photoCalib.getCalibrationErr(), calibrationErr)   E AssertionError: 161742302.08062094 != 161742302.08062097     "
Answer: 1303.0

User story: "Write an integration test for ATPtg to ATMCS as a SAL script and add it to ts_standardscripts.    There may be some overhead because this is the first script added to that package."
Answer: 35982.0

User story: "When the next RC2 is generated, the release note need to be updated with the latest issues included"
Answer: 10149.0

User story: "The description of DM Science Validation Scientist/Team in LDM-294 and LDM-503 need to be updated. The org chart in Figure 3 of LDM-503 needs to be updated"
Answer: 711942.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 the ci_lsst imsim tests they fail in the calibration construction phase with a bad key:  {code}  root INFO: Running: .../stack/DarwinX86/pipe_drivers/16.0-10-g0ee56ad/bin/constructBias.py ./tmp/imsim --rerun timj/tmp --id visit=3010000..3010009:3 -j 4  LsstCamMapper WARN: Unable to find valid calib root directory  CameraMapper INFO: Loading exposure registry from /Users/timj/work/lsstsw3/build/obs_lsst_new/tmp/imsim/registry.sqlite3  LsstCamMapper WARN: Unable to find valid calib root directory  bias FATAL: Failed: 'ccd'  Traceback (most recent call last):    File ".../stack/DarwinX86/pipe_drivers/16.0-10-g0ee56ad/python/lsst/pipe/drivers/constructCalibs.py", line 365, in __call__      result = task.runDataRef(**args)    File ".../stack/DarwinX86/pipe_drivers/16.0-10-g0ee56ad/python/lsst/pipe/drivers/constructCalibs.py", line 441, in runDataRef      expRefList, level="sensor", ccdKeys=self.config.ccdKeys)    File ".../stack/DarwinX86/pipe_drivers/16.0-10-g0ee56ad/python/lsst/pipe/drivers/constructCalibs.py", line 230, in getCcdIdListFromExposures      name = dictToTuple(ccdId, ccdKeys)    File ".../stack/DarwinX86/pipe_drivers/16.0-10-g0ee56ad/python/lsst/pipe/drivers/constructCalibs.py", line 196, in dictToTuple      return tuple(dict_[k] for k in keys)    File ".../stack/DarwinX86/pipe_drivers/16.0-10-g0ee56ad/python/lsst/pipe/drivers/constructCalibs.py", line 196, in <genexpr>      return tuple(dict_[k] for k in keys)    File ".../miniconda/envs/lsst-scipipe/lib/python3.7/collections/__init__.py", line 1025, in __getitem__      raise KeyError(key)  KeyError: 'ccd'  Failed to process imsim   {code}    It is likely a problem with the configurations for imsim in that the default keys are being used rather than the ccdKeys override.
Answer: 343.0

User story: "The puppet deployment of the auxiliary telescope white light chiller component on the summit."
Answer: 654123.0

User story: "The puppet deployment of the auxiliary telescope white light source component on the summit."
Answer: 654125.0

User story: "The puppet deployment of the auxiliary telescope fiber spectrograph component on the summit."
Answer: 654126.0

User story: "The puppet deployment of the auxiliary telescope electrometer component on the summit."
Answer: 654127.0

User story: "The puppet deployment of the auxiliary telescope monochrometer component on the summit."
Answer: 654129.0

User story: "The puppet deployment of the auxiliary telescope control system on the summit   I assume this has to do with the scriptqueue and the associated scripts."
Answer: 654130.0

User story: "The puppet deployment of the auxiliary telescope active optic system component on the summit."
Answer: 654132.0

User story: "The puppet deployment of the auxiliary telescope pointing component on the summit."
Answer: 654133.0

User story: "The puppet deployment of the auxiliary telescope mount control system component on the summit."
Answer: 654135.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 puppet deployment of the auxiliary telescope pneumatics component on the summit."
Answer: 654136.0

User story: "The puppet deployment of the auxiliary telescope dome trajectory component on the summit."
Answer: 647515.0

User story: "The automated deployment of the auxiliary telescope hexapod component on the summit via kubernetes with machines provisioned by puppet."
Answer: 654139.0

User story: "The puppet deployment of the auxiliary telescope dome component on the summit."
Answer: 647518.0

User story: "The puppet deployment of the auxiliary telescope spectrograph component on the summit."
Answer: 654145.0

User story: "DM-15795 created DiaForcedSourceTask but currently none of the outputs are stored into the Ppdb. Depending on the outcome of DM-17553 either this will be done through the ScienceDataModel code currently being developed for DRP or from custom task based on what is already currently being done in ap_assocation for DiaSources"
Answer: 243673.0

User story: "Make sure the weekly under consideration for the next release candidate does not have significant regressions from the previous major release."
Answer: 9670.0

User story: "As soon as a new valid weekly build is identified, the next release candidate v17.0.rc2 shall be created."
Answer: 17247.0

User story: [~<USER> reports on slack:  {quote}In the dynamic detection, (1) I suspect that the call to `tweakBackground()` at  https://github.com/lsst/meas_algorithms/blob/master/python/lsst/meas/algorithms/dynamicDetection.py#L214  is not effective because it modifies only `exposure` and it does not modify `middle` , which is passed to `applyThreshold()` . The tweaked `exposure` will be thrown away when the instruction pointer goes out of the with-clause.  {quote}  I agree with his analysis.  I believe we do eventually make the tweak permanent, by calling {{tweakBackground}} a second time near the end of {{detectFootprints}}, this time on the image that is retained.  And the initial call {{tweakBackground}} does have a small affect, because the temporary image it is operating on *is* used to refine the set of peaks after the footprint regions have already been determined when {{doTempLocalBackground}} is true.  But it seems like it was intended to affect the image used for footprint-region detection ("middle") as well.
Answer: 60782.0

User story: "The DESC DM-DC2 team has agreed that the changes on the [https://github.com/lsst/obs_lsst/tree/u/<USER>run2.xi_stars_only_ref_cats] branch, should be merged to master and included in upcoming releases of obs_lsst.  This is in support of using a stars-only reference catalog for the Run2.1i processing, which will be our default."
Answer: 10183.0

User story: "Implementing RFC-570. Not sure what epic this belongs to."
Answer: 1963.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 I submit the query   {quote}SELECT ra, decl, w1mag, w1mag - w2mag FROM wise_00.allwise_p3as_psd   WHERE qserv_areaspec_circle(283.831250,-30.545278,0.20)=1  {quote}  through pyvo, the values in the result column "w1mag - w2mag" are all strings instead of floats. Manipulating the results with pandas seems to kind of work anyways, but it becomes excruciatingly slow.    I can check what the XML looks like with:  {quote}{{query_string = ("SELECT ra, decl, w1mag, w1mag - w2mag FROM wise_00.allwise_p3as_psd "}}   \{\{ "WHERE qserv_areaspec_circle(283.831250,-30.545278,0.20)=1 ")}}   {{query = pyvo.dal.TAPQuery(query=query_string, baseurl='http://lsst-lsp-stable.ncsa.illinois.edu/api/tap')}}   {{res = query.execute_stream()}}   {{res_str = res.read()}}   {{res_str[:1500]}}  {quote}  and I see:     {{<FIELD name="w1mag - w2mag" datatype="char" arraysize="*" />}}             
Answer: 861797.0

User story: "{{DcrAssembleCoaddTask}} is missing from [https://pipelines.lsst.io/v/daily/modules/lsst.pipe.tasks/index.html |https://pipelines.lsst.io/v/daily/modules/lsst.pipe.tasks/index.html,]and should be added."
Answer: 239.0

User story: "This ticket is to capture the work done to deploy and configure InfluxDB + kafka connect in the efd-kafka cluster while the deployment is not fully automated by Terraform. See DM-16776, DM-17513, DM-17531 and DM-17754."
Answer: 2.0

User story: "SAL text-based messages are converted to Avro by {{saltransform}} in DM-17282. {{saltransform}} also initializes the schema registry with the schema for the {{lsst.sal.*}} topics.    In DM-17461 we create the connector for InfluxDB and deployed the connector as part of the {{terraform-efd-Kafka}} deployment. If we want to auto-discover the {{lsst.sal.*}} topics from the schema registry when creating the connector, {{saltransform}} should be added to the {{terraform-efd-kafka}} deployment as well.    In this ticket, we compare two deployment strategies involving Terraform. First, we use the Terraform kubernetes provider to create the kubernetes objects needed to deploy {{saltransform}}. Second, we create a Helm chart to deploy {{saltransform}} and use the Terraform Helm provider to install the helm chart."
Answer: 18516.0

User story: "Following conversations around Feb. 8th 2019 in #dm-bootcamps (for some reason) it is noted that `obs_lsst` will need to be extended/enhanced to support BOT* data when it becomes available.    How this looks will depend on exactly when that happens, and whether version-able cameras are a reality by then, as this data will necessitate that.    *Bench for Optical Test - the IR2 test station where real data from the real camera will be taken as it is populated with rafts"
Answer: 53318.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: "Create a aiohttp-based app (like [https://github.com/lsst-sqre/sqrbot-jr)] that consumes Slack messages from SQuaRE Bot Jr and responds to messages with a phrase like {{@sqrbot-jr create project}} or {{@sqrbot-jr create file.}}    The next step would be to add the actual logic for instantiating the templates by integrating with templatekit and add an interactive workflow for the user to designate values that go in the templates."
Answer: 13087.0

User story: "The current instructions for building change controlled documents are a bit convoluted in that they require the use of cherry-pick and leave unmerged branches hanging around.  This works against the idea of using protected master branches and results in confusing usage of pull requests.    At the recent CCB meeting it was decided to change approach and use a new process involving {{git revert}} and merging of pull requests to master once the document has been released."
Answer: 233428.0

User story: "It's not a serverextension.  But I didn't used to get an error when trying to load it as one."
Answer: 233.0

User story: "Develop and support the active optics closed-loop simulation. This task will integrate the modules of ts_tcs_wep_phosim, ts_tcs_wep, and ts_tcs_ofcPython. This task will be a prototype of active optics closed-loop simulation. The prototype here will support the simulation of main telescope active optics system (MTAOS) in the final. This task is in the phase 2 of the development."
Answer: 24586.0

User story: When accessing a "shareable" URL under {{https://lsst-lsp-stable.ncsa.illinois.edu/nb/user/$USER/lab/tree/notebooks/}} to a notebook for which the accessing user does not have permission, JupyterLab reports:  {quote}Cannot find template: "403.html"   In "/usr/local/share/jupyter/lab/static"  {quote}  This is undesirable, compared to the result when accessing a "download" URL under {{https://lsst-lsp-stable.ncsa.illinois.edu/nb/user/$USER/files/notebooks/}}, which reports:  {quote}403: Forbidden   The error was:   user ktlim was not allowed.  {quote}
Answer: 30143.0

User story: "This task covers the time spent to support M1M3 Mirror Lab testing."
Answer: 4147.0

User story: "The result of this RFC will be a proposal to the SE subsystem.  It will be put forward to the CCB and if approved, become a change controlled LSE document.  At that point, we can also add a requirement to the OSS that refers to that LSE document, if desired."
Answer: 11550.0

User story: "See the attached files.  [^doesnt_pass.py] fails {{flake8}} as expected.  It is true that {{lsst.afw.image}} is imported but not used.  With a slight modification,  [^passes.py], to use {{lsst.afw.image}} in the function, {{flake8}} passes.  However, notice that there is still an unused import below the import for {{lsst.afw.image}}.  Apparently, {{flake8}} does not notice this with the current stack configuration.    In order to reproduce, simply say:  {code}  flake8 <filename>  {code}"
Answer: 3051.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 ATCS node on the hardware cluster was not responding to pings.  I rebooted it and it came back but only the 10.0.100.141 port was   automatically active."
Answer: 4191.0

User story: "Characterization Report for 17.0 release is required."
Answer: 30625.0

User story: "In preparation of the 17.0 release, relevant information for the release note shall be gathered:   * list of issue resolved since last release   * Narrative describing the release"
Answer: 8546.0

User story: "Configure each of the private network machines on 10.0.100 subnet to refer to   the bastion yum repo. This involves adding the appropriate file to /etc/yum.repos.d"
Answer: 69539.0

User story: "[~<USER> and I have found that some of the default parameters in scarlet need to be modified to more useful values.     1. Normalizing the morphology (S matrix) so that the peak value is set to unity is the most effective way to break the SED/morphology degeneracy, as opposed to the current method of normalizing the SED (A matrix). This provides a method to separate sources with similar colors but very different intensities and also converges more quickly than the current default normalization.    2. Turning off Nesterov acceleration. There appears to be an issue with combining our proximal gradient method with Nesterov acceleration, making the optimization algorithm asymptotic. It also appears to be even more unstable with the new normalization scheme, however using S matrix normalization _without_ acceleration still runs faster than A matrix normalization _with_ acceleration.    This ticket will also create a change log in scarlet to keep track of these and other modifications to keep users up to date with the changes. It will also make it easier to keep stack users up to date when updated versions of scarlet are imported into the stack."
Answer: 4907.0

User story: "This ticket has been expanded to investigate two effects that we are seeing in blends while using PSF matching.    1. We commonly see color gradients in the residuals when running scarlet on real HSC data. This is the main issue with running scarlet on real science data.    [~<USER> and I believe that this is due to a misalignment of the PSF kernels given by the DM pipeline as opposed to their offsets in the image. In other words, it looks like the PSF kernel gives a PSF that is centered on the central pixel while the actual PSF in the image may have offsets between the bands. This needs to be verified, and regardless we need to make sure there is agreement between where the stack says the PSF should be centered and where scarlet applies it.    So part of this ticket is to determine the cause of the color fluxes and the rest is to fix the issue.    2. We also see rings around the centers of bright sources, with centers underestimated by the model and a ring around the center that is overestimated by the model."
Answer: 111401.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: "Running {{AssembleCoaddTask}} with default settings produces multiple warnings: {{assembleCoadd WARN: Unable to remove mask plane NOT_DEBLENDED: Invalid mask plane name: NOT_DEBLENDED}}    These warnings are caused by the default value for the config option {{removeMaskPlanes}} including {{NOT_DEBLENDED}}, and would be fixed by removing it from the default."
Answer: 155542.0

User story: Comparing HSC-RC2 reprocessing by stack w_2019_02 and w_2019_06, we've got a new set of processCcd errors. They fail at calibrate.astrometry.matcher with   {noformat}    File "/software/lsstsw/stack_20181012/stack/miniconda3-4.5.4-fcd27eb/Linux64/meas_astrom/16.0-24-gfa57b64+1/python/lsst/meas/astrom/matchPessimisticB.py", line 278, in matchObjectsToSources      raise RuntimeError("Unable to match sources")  {noformat}    The 60 data ids of the new failure set is as follows    {noformat}  --id visit=34338 ccd=75  --id visit=34362 ccd=38  --id visit=34382 ccd=43  --id visit=34384 ccd=88  --id visit=34402 ccd=61  --id visit=34422 ccd=42  --id visit=34424 ccd=2  --id visit=34448 ccd=79  --id visit=34450 ccd=25  --id visit=34478 ccd=21  --id visit=34482 ccd=50  --id visit=34644 ccd=72  --id visit=34690 ccd=39  --id visit=36140 ccd=30  --id visit=36170 ccd=18  --id visit=36182 ccd=80  --id visit=36212 ccd=34  --id visit=36234 ccd=82  --id visit=36240 ccd=0  --id visit=36258 ccd=73  --id visit=36428 ccd=61  --id visit=36432 ccd=23  --id visit=36492 ccd=50  --id visit=34942 ccd=44  --id visit=36762 ccd=18  --id visit=36774 ccd=24  --id visit=36792 ccd=34  --id visit=36808 ccd=26  --id visit=36828 ccd=16  --id visit=36828 ccd=73  --id visit=26046 ccd=32  --id visit=26050 ccd=74  --id visit=26058 ccd=34  --id visit=26060 ccd=70  -id visit=26072 ccd=12  --id visit=26080 ccd=66  --id visit=26084 ccd=64  --id visit=23864 ccd=12  --id visit=1308 ccd=40  --id visit=23224 ccd=59  --id visit=23232 ccd=32  --id visit=27106 ccd=33  --id visit=27106 ccd=41  --id visit=27128 ccd=26  --id visit=27134 ccd=28  --id visit=440 ccd=92  --id visit=452 ccd=35  --id visit=452 ccd=42  --id visit=472 ccd=30  --id visit=1246 ccd=19  --id visit=19696 ccd=20  --id visit=30500 ccd=20  --id visit=1180 ccd=89  --id visit=1184 ccd=26  --id visit=1194 ccd=26  --id visit=360 ccd=26  --id visit=22628 ccd=18  --id visit=22664 ccd=26  --id visit=23046 ccd=26  --id visit=23050 ccd=84  {noformat}  
Answer: 6090.0

User story: "This ticket is to deploy [https://astro-metadata-translator.lsst.io|https://astro-metadata-translator.lsst.io/] to LSST the Docs. Since it's a standalone Python package, the deployment will be done from Travis CI (following the pattern of SQuaRE's Python packages).    As well, we'll add {{astro_metadata_translator}} to the intersphinx configuration of pipelines.lsst.io so that links will be automatically resolved."
Answer: 336.0

User story: "Put together a Vault taxonomy and hierarchy to give us a fairly straightforward key management infrastructure so we can do delegated secret management in a sane way."
Answer: 11927.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: "Satisfies action item from November 2018 DMLT."
Answer: 32208.0

User story: "- Make qserv_deploy configuration clearer:    * Mount cfg/tmp path correctly:  {code}  fjammes@[qserv-deploy]:~ # ls -rtl /etc/qserv-deploy/  total 24  drwxrwxr-x 3 fjammes fjammes 4096 Jan 25 15:17 gcloud  drwxr-xr-x 4 fjammes fjammes 4096 Feb  1 11:41 tmp  -rw-rw-r-- 1 fjammes fjammes 1019 Feb 12 11:35 env.sh  -rw-rw-r-- 1 fjammes fjammes  605 Feb 12 11:35 env-infrastructure.sh  -rw-rw-r-- 1 fjammes fjammes  679 Feb 12 11:38 env-gke.sh  drwxrwxr-x 4 fjammes fjammes 4096 Feb 12 11:50 dot-kube  {code}  - Allow to easily manage several configuration.  - Record which qserv_deploy version was used to install a given cluster  - Add pseudo /etc/password for NFS/LDAP setup?  - Test it to create a GKE cluster  - Test it on CC-IN2P3 cluster  - Update CI"
Answer: 41353.0

User story: "The interpolation of MERRA-2 3-D AOD tables at LSST site is complicated by the orography of the Andes : data eastward of the site coordinates are not going down to the altitude of the telescope. A reliable extrapolation of the AOD has to be determined."
Answer: 83792.0

User story: "It has been decided in Pathfinder meetings that we are gonna go ahead and write rpms for puppet deployment of Level 1 services. This ticket captures the work done for implementing rpms."
Answer: 11616.0

User story: "As DM-17669 has been merged, all TS8 butler repos need to be re-ingested. Otherwise the w_2019_06 stack and onward can't read those repos. "
Answer: 28952.0

User story: Currently sconsUtils requires that doxygen strings be used to create the documentation. This is done because sconsUtils requires that SCons be imported and that is only possible if SCons is importing sconsUtils. Since pydoc and sphinx import python code to extract documentation this makes it hard to use numpydoc.    For example:  {code}  $ pydoc lsst.sconsUtils  problem in lsst.sconsUtils - ImportError: lsst.sconsUtils cannot be imported outside an scons script.  {code}    It seems though that this is easy to work around. The following patch allows {{pydoc}} to work and opens the possibility of migrating sconsUtils away from doxygen.    {code:diff}  diff --git a/python/lsst/sconsUtils/__init__.py b/python/lsst/sconsUtils/__init__.py  index ee9f02a..6e3c456 100644  --- a/python/lsst/sconsUtils/__init__.py  +++ b/python/lsst/sconsUtils/__init__.py  @@ -1,4 +1,13 @@   # Explain what happens when you try to import outside scons  +# When building documentation you want to force a SCons import  +import os  +import sys  +  +if ("pydoc" in sys.modules or "sphinx" in sys.modules) and "SCONS_DIR" in os.environ:  +    scons_path = os.path.join(os.environ["SCONS_DIR"], "lib", "scons")  +    if scons_path not in sys.path:  +        sys.path.append(scons_path)  +   try:       import SCons.Script   except ImportError:  {code}  
Answer: 7321.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: "Now that jointcal applies the colorterms, we can look at much smaller differences in how meas_mosaic an jointcal match the to reference catalog. Some observations. There is a shift that jumps from    * from 3 to 5mmag in HSC-I  [meas_mosaic_I|https://lsst-web.ncsa.illinois.edu/~<USER>RC2_w_2019_02/pipe_analysis/qaPlots/HSC-I/tract-9615/plot-t9615-HSC-I-matches_mag-psfMagHist.png] vs. [jointcal_I|https://lsst-web.ncsa.illinois.edu/~<USER>RC_QA/w_2019_02_colorterms/HSC-I/tract-9615/plot-t9615-HSC-I-matches_mag-psfMagHist.png]   * 6 to 12mmag in HSC-R [meas_mosaic_R|https://lsst-web.ncsa.illinois.edu/~<USER>RC2_w_2019_02/pipe_analysis/qaPlots/HSC-R/tract-9615/plot-t9615-HSC-R-matches_mag-psfMagHist.png] vs. [jointcal_R|https://lsst-web.ncsa.illinois.edu/~<USER>RC_QA/w_2019_02_colorterms/HSC-R/tract-9615/plot-t9615-HSC-R-matches_mag-psfMagHist.png]   * 8 to 8mmag (no change in HSC-G!) [meas_mosaic_G|https://lsst-web.ncsa.illinois.edu/~<USER>RC2_w_2019_02/pipe_analysis/qaPlots/HSC-G/tract-9615/plot-t9615-HSC-G-matches_mag-psfMagHist.png] vs. [jointcal_G|https://lsst-web.ncsa.illinois.edu/~<USER>RC_QA/w_2019_02_colorterms/HSC-G/tract-9615/plot-t9615-HSC-G-matches_mag-psfMagHist.png]    and the 3 mmag shift in the `w` principle component from jointcal to meas_mosaic  [new_jointcal_gri|https://lsst-web.ncsa.illinois.edu/~<USER>RC_QA/w_2019_02_colorterms/color/tract-9615/plot-t9615-griCModel-wFit-fit.png]  which is probably a manifestation of the offsets above (and just another way of looking at it)    I don't know if these are significant or not. Will those with more expertise comment on whether this is a problem or not.     *NOTE: these comparisons were done with meas_mosaic before DM-13054. If [https://community.lsst.org/t/incorrect-reference-magnitude-errors-from-photocaltask/3581] affects meas_mosaic too, I propose we wait for* [~<USER>*'s w_2019_06 run next week before we spend time thinking about this.* "
Answer: 121682.0

User story: "The first draft of the tasks to insert fakes sources was showing source magnitude offsets between the inputs and outputs, background offsets, etc... This ticket captures the work done to:   * Learn about the all the steps in the DRP pipelines that could have given birth to these changes.   * Make initial QA plots to validate that the fakes were being inserted correctly   * Investigate the sources of input vs. output offsets. "
Answer: 118.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: "These packages have doc/ directories that don't fit the current standards (mostly because they include package documention when they really only should have module documentation). This ticket is to fix these packages:   * afw   * base   * coadd_utils   * daf_butler   * display_ds9   * ip_diffim   * ip_isr   * jointcal   * log   * meas_algorithms   * meas_deblender   * meas_extensions_photometryKron   * meas_extensions_shapeHSM   * meas_extensions_simpleShape   * meas_modelfit   * obs_base   * obs_cfht   * obs_lsstSim   * obs_test   * pex_exceptions   * pipe_base   * pipe_drivers   * shapelet   * utils   * validate_drp   * verify    Also, there's a typo in the title of the {{lsst.meas.extensions.simpleShape}} module docs."
Answer: 4045.0

User story: "Provide examples of a few (perhaps 10?) bad subtractions to [~<USER>. He'll need a description of why it's wrong (if it's not obvious) and instructions for how to reproduce (ie, which data, what code to run, etc)."
Answer: 34950.0

User story: "[~<USER> has identified some bad subtractions while running ap_pipe. She will provide a short list (a few DIASources) on this ticket together with instructions to reproduce. For each one:    - Reproduce the problem;  - Dive into the ip_diffim code and see if you can identify what caused the problem;  - If it's fixable, file a ticket to fix it."
Answer: 261367.0

User story: "Update LPM-251 to include Open Data Framework and rework intro and title."
Answer: 54957.0

User story: "DAQForwarder hasn't been run on the NCSA test stand for a while since all of our efforts were focused on Auxiliary Telescope. This effort will normalize the forwarder so that it can be ran and extract images from daq hardware at NCSA."
Answer: 34846.0

User story: "Set up test coverage monitoring for OpenOrb (our adopted orbit integration engine).    This includes:    * Having a make target to run the test coverage tools as 'make coverage'   * Have this target automatically invoked by one of the CI runs   * Have the results uploaded to a cloud test coverage visualization service.    We will be using [codecov.io|http://codecov.io] as the service for visualization of coverage reports.    The work will be on [https://github.com/<USER>oorb/tree/ci-and-codecov], and will be PR-ed upstream upon completion. It depends on DM-17814 being merged."
Answer: 177374.0

User story: "Set up continuous integration for OpenOrb (our adopted orbit integration engine).    This includes:    * Building on Mac and Linux with Anaconda compilers with Python 2.7, 3.6, 3.7   * Building on Linux (Ubuntu 16.04) with Ubuntu-supplied compilers and Python 2.7 and 3.5   * Builds are to be triggered by pushes/PRs to GitHub repository    We will be using the Azure Pipelines service, as we did with pytrax (DM-17027).      The work will be on https://github.com/<USER>oorb/tree/ci-and-codecov, and will be PR-ed upstream upon completion. It depends on DM-17814 being merged."
Answer: 177378.0