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: "Currently there is no WCS information in the header(s). This would be desired for image display in multiple tools as they expect a specific keywords. Note that this should only be the basic set of keywords required to facilitate quick calculation of telescope offsets (etc) and will not be used for final data products.    We need to add some simple WCS to segment headers for the AT using fixed CRPIX and CRVAL (from boresight location) and CD (rotation and pixel scale) derived by the Header Service. The mapping of WCS per segment is defined in section 9.4 of LCA-13501. The header service can computed the CD matrix values for each segment based on the definition of LCA-13501 and ROT keyword.         LATISS to have CRPIX (constants), "
Answer: 385661.0

User story: "The new default (after DM-18147) of  /datasets/hsc/repo/  Bright Object Masks is /datasets/hsc/BrightObjectMasks/GouldingMasksS18A   Goulding Bright Object Masks have separate files for HSC-G/HSC-I/HSC-R/HSC-Y/HSC-Z but don't have individual files for narrow bands.    This means coadd tasks of filter=NB0921 don't have brightObjectMask, e.g.   {noformat}  WARN  2019-05-05T01:30:21.819-0500 coaddDriver.assembleCoadd: Unable to read brightObjectMask for DataId(initialdata={'tract': 9813, 'filter': 'NB0921', 'patch': '7,0'}, tag=set()): No locations for get: datasetType:brightObjectMask dataId:DataId(initialdata={'tract': 9813, 'filter': 'NB0921', 'patch': '7,0'}, tag=set())  {noformat}    Make NB0921 links to use HSC-Y, and NB0816 to use HSC-I. "
Answer: 132463.0

User story: "Incorporate the AT Telescope pointing component from the CSC ATPointingComponent into the header service. The mapping is defined here    [https://confluence.lsstcorp.org/display/SYSENG/Auxiliary+Telescope+Header+Information+Topic+Mapping]         The implementation requires    1) Update the yaml configuration file and template (if not changed already) to use the information defined in the topic mapping.    2) Change the simulation of the messages, by updating the simulation code to send the event/Telemetry for the ATPointingComponent     "
Answer: 24374.0

User story: "Building on the code written in DM-17490, produce a task which can identify defects"
Answer: 28897.0

User story: "Pytorch requires MKL (at least to do any of the things Scarlet needs it to do).    We traditionally build without MKL because it provides a limited FFTW that doesn't support a deprecated API that we use in meas_base (DM-8146).    The intel_openblas that conda's pytorch installs also causes problems with the number-of-threads inspection in our base package.    Disable both of these temporarily (at compile time) to see if that's enough to make conda's pytorch work."
Answer: 18508.0

User story: "We currently add rather than set {{OBSTYPE}} in e.g. `constructBias.py`.  This was broken once {{calculateOutputHeaderFromRaws}} started setting the output header, and potentially that included {{OBSTYPE}} (and if it's {{None}} the code crashes)"
Answer: 4053.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 enumeration (integers) of the CSC states need to be updated in salpytools. Instead of using the detailed states, it should the SAL__STATE_CSCNAME from now one."
Answer: 4103.0

User story: It looks like the template PSF is not warped in image differencing. See lines 407-411 of {{imagePsfMatch.py}} in {{ip_diffim}}. This leads to a much broader PSF being used for calculating the matching kernel if the template is at a finer plate scale than the science image. Also, if the PSF is elliptical, it may end up with the wrong rotation, and this may be causing an increase in "quadrupole" mis-subtractions.
Answer: 4472.0

User story: "Update ts_phosim (from ts_tcs_wep_phosim) to use eups and documenteer and add dependency to ts_wep. This is to unify the package manager and reduce the code redundancy. This task will also update the configuration files to use the yaml format."
Answer: 10031.0

User story: With {{w_2019_18}}, running skyCorrection.py with HSC data gave the following error:       {noformat}  afw.cameraGeom.utils.makeImageFromCamera ERROR: Unable to fit image for detector "0_31" into image of camera:    File "src/image/Image.cc", line 183, in void lsst::afw::image::ImageBase<PixelT>::assign(const lsst::afw::image::ImageBase<PixelT>&, const lsst::geom::Box2I&, lsst::afw::image::ImageOrigin) [with PixelT = float]      Dimension mismatch: 522x256 v. 256x522 {0}  lsst::pex::exceptions::LengthError: 'Dimension mismatch: 522x256 v. 256x522'  {noformat}    This error didn't appear with the {{w_2019_14}} stack.     Besides detector "0_31", it also happened to  detector "1_35" , detector "0_35", and detector "1_31" -- the four edge CCDs that lay 90 deg different from others.     An example to reproduce,   {noformat}  skyCorrection.py /datasets/hsc/repo --calib /datasets/hsc/repo/CALIB --rerun  RC/w_2019_18/DM-19151-sfm:private/user/name --time 90  --id visit=34338 --cores 24   {noformat}    
Answer: 33.0

User story: "As part of the testing of and development of CSC, and in particular for the L1 NCSA Test Stand we need a utility that can test and verify the reception and acks of command for transitioning states. This is particularly useful when testing new version of SAL."
Answer: 418.0

User story: "Draft release policy document LDM-672 and put to RFC"
Answer: 76208.0

User story: "Write the DM Science Monthly report for April"
Answer: 19363.0

User story: "scarlet has internal diagnostic information and flags that are set but not passed to the LSST stack. {{ScarletDeblendTask}} needs to be updated to update the catalogs with the relevant flags."
Answer: 14343.0

User story: "Docs are past column 79, fix"
Answer: 33.0

User story: "Add the proper functionality to extend __init__ methods in meas_extensions_scarlet."
Answer: 78.0

User story: "Laptop and main computer is with Doug. I will check the startup and software installed on the PC and laptop before we ship it to Chile. Review documentation that were delivered along with the devices."
Answer: 182797.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: "For the dds version of salobj I am presently using one dds.WaitSet per topic, which takes one thread per topic. However, it may be possible to use dds select to have a single thread that reads all topics. That should be more efficient and scale better for the Watcher. Look into this and implement it if practical."
Answer: 14445.0

User story: "Deliver 2  commandlinetask to the project :   1- One to fetch from MERRA-2 servers the tables with atmospheric parameters \{Pressure, AOD, PDW, Ozone} (x,y,z,t) for a given date, around LSST site.   2- the other to (x,y)-interpolate and z-integrate the parameters above the site"
Answer: 236767.0

User story: "Use jointcal instead of meas_mosaic!     We've done sufficient QA, integration work and improvements to believe this is now working at least as well as meas_mosaic. This doesn't require an RFC because it just affects obs_subaru  (RC2 reprocessing and future HSC data releases)."
Answer: 262.0

User story: "The driver to {{afw.cameraGeom.showCamera}} in pipe_drivers's {{visualizeVisits}} fails to take {{nQuarter}} into account.  Please fix this.     "
Answer: 12.0

User story: "Building on recent work to enable bootstrapping the Gen3 ci_hsc dataset with minimal reliance on gen2convert (DM-19614, DM-19615, DM-19622, DM-19531, DM-19272) and improvements to gen2convert itself (DM-18023), write a task/script that can be used to similarly bootstrap other Gen3 repos, starting with RC2.    Steps will include:   * register instrument(s)   * add curated calibrations, via Instrument.writeCuratedCalibrations   * register skymaps(s)   * ingest raws, via RawIngestTask   * add Gen2-calib-repo calibrations, refcats, and BrightObjectMasks via explicit, lower-level calls to gen2convert code in daf_butler.    I do not currently plan to include actually creating the empty repository, which will save this task from having to somehow read in and apply overrides to butler yaml configuration."
Answer: 19265.0

User story: "more Alpine incompatos in container build script..."
Answer: 17.0

User story: "Recent change of Jenkins build workers to Alpine broke Qserv container build scripts"
Answer: 72.0

User story: This ticket is to track the time spent participating in the Operations Rehearsal #1 which will run from Mon, May 6, 2019 through Thurs, May 9, 2019.  In particular, I have been asked to provide "QA" support.
Answer: 24063.0

User story: "Implement a loading service within existing Replication System's workers. The service will initially support data in the TSV format. The services will create MySQL partitions in the chunk tables as per the super-transaction identifiers. Implement a command-line application which would accepts pre-partitioned TSV files and perform all required interactions with the Master Replication Controller (via the HTTP REST API). There will be a suite of simple integration and performance testing applications (scripts) to drive the parallel loading."
Answer: 292045.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "It was noted on RFC-595 that the creation of the Defects text files to be stored in the data repositories is distinct from Defects.  It would be more useful for people creating defects lists if the Defects class could serialize to the text format.    [~<USER> also requests that metadata be stored in the text files (at least the format version number and the detector name and instrument).  To satisfy that requirement I will see if I can write out in the Astropy ECSV format."
Answer: 5870.0

User story: "All activities as the DM liaison to LSST EPO"
Answer: 157088.0

User story: "MultiProFit currently fits ellipse shapes using the major axis, axis ratio, position angle parameterization. While easily understood, the position angle is problematic - it is unconstrained for near-circular ellipses and has periodic boundary conditions. This ticket will switch to fitting sigma_x, sigma_y and rho from the covariance matrix [[sigma_x**2, rho*sigma_x*sigma_y], [rho*sigma_x*sigma_y, sigma_y**2]], which is well-behaved and has reasonable limits of sigma_x, sigma_y >= 0 and -1 <= rho <= 1."
Answer: 50497.0

User story: "sqlalchemy has a few different ways to insert multiple objects at a time, change to one that works across more databases reliably."
Answer: 323.0

User story: "DM-17633 failed to lowercase PosixDatastoreRecords, as it's defined in a totally different way from the rest of the schema.  Fix that."
Answer: 316.0

User story: "Given all the recent changes we need to document and define better ways to do deployment and services, this document will address those issues"
Answer: 332578.0

User story: "Currently the butler configuration used for gen 3 testing in ci_hsc is hard coded into the lsst.ci.hsc.gen3 module.  This makes it hard to use for oracle testing where we want to override the configuration.  Update gen3.py to be a class allowing an override butler and add command line to the gen3.py script to use that functionality."
Answer: 7454.0

User story: "PipelineTask preflight supports taking inputs from multiple collections, including specifying that certain DatasetTypes should be retrieved from specific collections.  [~<USER> has calibration-production use cases for doing that with just a Butler, which, if implemented, might also lead to some simplifications elsewhere (e.g. using the QueryBuilder classes in more Registry methods).    -It could _possibly_ also be a first step towards a lazier, more Gen2-like approach to collection-chaining, which could be nice if we either find out that the new model doesn't support existing use cases in other ways of it leads to DB performance problems due to a massive number of tag records.-"
Answer: 470758.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "In order to be able to generate a Gaia (or PS1-DR2) reference catalog in a reasonable amount of time, we need a way to process files in parallel. The existing IngestIndexReferenceObjectsTask is not capable of running in parallel. One approach that should be fairly simple is to use multiprocessing plus file locking: lock each output catalog before appending."
Answer: 69579.0

User story: "The gen3 butler storage class in IsrTask does not match what it is ingested as, fix this."
Answer: 576.0

User story: "Transmission curves should be written to the butler when writing human curated calibration products"
Answer: 593.0

User story: "Affinity needs to be added to XrdSsiResource jobResource in qdisp::Executive so that it can be tested by itself."
Answer: 7063.0

User story: "GPFS direct mounts need a little more work to work in dask."
Answer: 143.0

User story: "Add a configuration to sqrbot-jr so that Slack messages and other types of events are only retained for a small amount of time (such as 30 minutes)."
Answer: 1491.0

User story: "* 30 min Presentation on the LSST science drivers, pipelines and data products and LSST commissioning.    * 1.5hr session on LSST Science Platform (talk + 2 demos). These will be non-interactive demonstrations. Main science interests of participants are: Galaxies, TVS and cosmology.    ** ProcessCCD demonstration   ** Portal notebook    ** Accessing catalogs with the TAP service"
Answer: 79379.0

User story: "In a regular channel, Templatebot responds to \{\{app_mention}} Slack events. It doesn't seem to be currently receiving those. This ticket is to:   * Ensure that sqrbot-jr is sending Kafka messages for app_mention events   * Ensure that templatebot is recieving those app_mention events."
Answer: 1650.0

User story: "Test:  DM-19601"
Answer: 59200.0

User story: "Add the logic discussed in ticket https://jira.lsstcorp.org/browse/DM-18642 :       So we should certainly add a SAL command, regardless. (To do a position reference)  We should avoid movement in the disabled state, so on the start command, check the reference. If it's good, then continue as normal without re-referencing. If the reference is bad, then on enable, execute a reference and tell the user a reference is happening and therefore it might take more time.    Also add a reference event that checks and announce if the controller is properly referenced."
Answer: 59201.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: "Only one wdb::SQLBackend object should be connected to a mariadb server at time due to the creation and destruction of temporary tables. Currently, SQLBackend terminates the worker is it detects that a different worker has taken ownership of the lock table (see SQLBackend::_memLockAquire). If the connection is broken and the lock table still contains the id of this worker, the mariadb client could not have gone down as the information is in a row in an in memory table. If there's no row,  mariadb probably crashed, and the worker will terminate.         Problems:   * SQLBackend uses the pid for its user id, and since these run in Docker containers, they are probably not unique. It's likely they all have pid 1. A better id is needed, maybe uuid.   * Ownership is only checked when temporary tables are acquired or released. It would may be worth checking every time the connection to the mariadb client is lost and restored. If this worker lost ownership via mariadb death, it makes sense for the worker to restart at the same time.          should be changed so that behaves properly with Kubernetes rules. It needs to handle the mariadb service dying and coming back correctly.   * If the connection to mariadb is lost, the worker needs to check if it is still the owner when the connection is restored. If it is not the owner, it needs to establish ownership and destroy all temporary tables as done in SQLBackend::_memLockAquire. Note: all activily running queries "
Answer: 391427.0

User story: "We should do new ap_pipe reruns on the HiTS2015 dataset approximately monthly with the latest weekly stack. In this case, we will not regenerate the coadd templates and will just use the CompareWarp coadds which are a few months old."
Answer: 43289.0

User story: "This is a duplicate of DM-19485.    https://github.com/lsst/daf_butler/commit/315427929f339c8e669c994ccabd8daeadc1e503 was incorrectly labelled as “DM-19585” on merge, when it should've been DM-19485. Scripts which attempt to look up the ticket corresponding to the merge — as used in generating release notes, for example — will therefore find this ticket. It therefore exists only to provide a signpost to DM-19485."
Answer: 30.0

User story: "The butler yaml configuration system might need some tweaking. Investigate [~<USER>'s problem and possibly adjust how overrides work."
Answer: 2987.0

User story: "Submit cases to the ADlink issue management system and assist with   investigation on the LSST side (of dds native python interface usage)"
Answer: 18919.0

User story: "Attend planning meetings, review documents and software in preparation  for  the planned June workshop on TMA software at Tekniker"
Answer: 18922.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: "DM-17981 introduces a {{Storable}} interface that can be used to store arbitrary classes in a {{GenericMap}}. Add {{Storable}} as a mixin to the following classes:  * {{lsst::afw::geom::SkyWcs}}  * {{lsst::afw::cameraGeom::Detector}}  * {{lsst::afw::image::Filter}}  * {{lsst::afw::image::PhotoCalib}}  * {{lsst::afw::detection::Psf}}  * {{lsst::afw::geom::polygon::Polygon}}  * {{lsst::afw::image::ApCorrMap}}  * {{lsst::afw::image::CoaddInputs}}  * {{lsst::afw::image::VisitInfo}}  * {{lsst::afw::image::TransmissionCurve}}  * {{lsst::daf::base::PropertySet}}  "
Answer: 53395.0

User story: "Compilers ({{g\+\+}}, {{clang\+\+}}) often produce color outputs (e.g., the word {{error}} is in red, and important paths are boldfaced) when run on the command-line, but do not when run under {{scons}}. I've just discovered [how to enable color output under {{scons}}|https://stackoverflow.com/a/9954572/834250], which I propose to implement. It merely involves propagating the {{TERM}} envvar through {{scons}}.    I know that {{scons}} deliberately doesn't propagate envvars, but we propagate some (e.g., {{TEMP}}, {{EUPS_DIR}}); I propose to add {{TERM}} to this list. I don't believe it should affect the compilation of anything, but only the format of the outputs."
Answer: 8857.0

User story: "Firefly doesn't work in the new regime."
Answer: 1888.0

User story: "Update ts_ScriptQueue to use the version of ts_salobj based on dds. This is primarily intended to exercise the new version of ts_salobj."
Answer: 34022.0

User story: I don't remember an announcement of this deprecation for maskPixelsFromDefectList(), but more to the point the backwards-compatibility code doesn't work:  {code}  @deprecated(reason="Replaced by Defects.maskPixels() (will be removed after v18)",              category=FutureWarning)  def maskPixelsFromDefectList(maskedImage, defectList, maskName='BAD'):```  {code}  used to accept a `list`, but now it assumes a `DefectList`    I have a fix -- stay tuned
Answer: 10.0

User story: "take a file every N second s and put it in another directory"
Answer: 12692.0

User story: "Implement efficient methods for computing and returning the gradient of the log likelihood with respect to input parameters for Gaussian mixture models, which should improve fitting performance."
Answer: 41671.0

User story: "Reprocess the HSC RC2 dataset, as defined in DM-11345, using Stack w_2019_26. Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{jointcal}}, {{skyCorrection.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}}. "
Answer: 105388.0

User story: "Run jointcal with HSC-RC2 and w_2019_18"
Answer: 10390.0

User story: "Run pipe_analysis scripts   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    and validate_drp   # matchedVisitMetrics.py   # validateDrp.py   # reportPerformance.py    Upload the validate_drp metrics (json files) to SQuaSH:   # dispatch_verify.py    with the w_2019_18 RC2 outputs from DM-19151"
Answer: 18845.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: In C++, {{lsst.afw.typehandling.GenericMap}} is a class template with a single template parameter, the key type. Since the key is likely to only be "simple" types like integer or strings, {{GenericMap}} is well-suited for use with {{lsst.utils.TemplateMeta}}.    Priority: minor, as currently there is only a string version of {{GenericMap}} in Python and no demand for alternatives.    Note that this will make the Python API slightly more confusing, since the new Python {{GenericMap}} would have the restriction that all keys must be of the same type, but not of any particular type. (Though in practice, I can't imagine a use case for heterogeneous keys.)
Answer: 73383.0

User story: "The {{meas_deblender}} package has become a bit unruly, with a lot of unnecessary code for the new scarlet deblender. So a new {{meas_extensions_scarlet}} package will be created to wrap the new version of scarlet, with the goal of eventually retiring {{meas_deblender}}. This ticket will see both the creation of the new package and the API to wrap scarlet v0.5."
Answer: 79593.0

User story: Following the ticket on angstrom exponent 2-D table, it appears that 3-D data would be needed. We are wondering why such a table is not available on the MERRA-2.    Two emails (April 17th and April 29th) have been sent to MERRA-2 people     "  Dear Arlindo,     Thank you for your previous answer regarding MERRA-2 tables.     I am still investigating how MERRA-2 could assist atmospheric transparency monitoring for ground based astronomy.  I am now wondering if the Total Aerosol Angstrom parameter that is given in table _tavg1_2d_aer_Nx (M2T1NXAER): Aerosol Diagnostics_   Would also be available as a function of altitude ?     I don’t find such a 3-D columns in tables  [https://gmao.gsfc.nasa.gov/pubs/docs/Bosilovich785.pdf]     Thank you in advance for you help,     Augustin   "
Answer: 245823.0

User story: "The analysis of the long term monitoring of atmospheric parameters above telescopes shows two trends : some parameters exhibit a clear, dominant, annual modulation (ozone and some aerosols) while others appear to vary in a less predictable manner (pwv, some other aerosols).    An hypothesis is that it depends on the mean altitude of the components : the higher this altitude, the more regular the modulation (ozone is mostly in the tropopause while pwv is larger near the ground).    The same hypothesis seems to be validated when looking at the aerosol species     [^aod_profiles.pdf]         This work can be used to inform the observing strategy of the A.T. : Ozone from MERRA-2, PWV from A.T. and mixed approached for aerosols.     "
Answer: 29153.0

User story: "This story deploys the kafka writers (which write only to the cloud, not a local database) to publish SAL data from the pLAN network. A container with the writers can be deployed on pontus (10.0.100.200). [~<USER> has volunteered to help with the container aspects if required.     "
Answer: 182802.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 DM-19290 is available, use it for the Calib deprecations."
Answer: 71955.0

User story: "Some form of report or presentation will be required for the JDR/JSR on the LSP review. "
Answer: 182984.0

User story: "In conjunction with the LSP meta-CAM, devise responses to the LSP review recommendations to see if there are additional important points or areas of concern that should be captured as LIT tickets or raised to senior management and the LSP team. "
Answer: 295190.0

User story: "The DM admins can help with entering LIT tickets"
Answer: 174185.0

User story: "Review the recommendations in the LSP review report, flatten the structure so that 1 item can be mapped to 1 LIT ticket.      "
Answer: 83407.0

User story: "Vendor released latest version of pointing component. Initial tests showed some issues with the component that need to be addressed and may have shown an issue with SAL 3.9/SalObj 3.11.0. This task will be used to continue testing the pointing component  and SAL.     Following Dave's suggestion I will spin up a EFD for the components to monitor the SAL traffic. I will also use this task to document a procedure on running integration and test on stage machines.     Documentation will go here:     https://confluence.lsstcorp.org/display/LTS/Integration+Testing+and+Deployment+Development+Procedure    "
Answer: 14568.0

User story: "For complex problems, we need to be able to slice and dice the logs over multiple kubernetes pods to piece together what happened.  I'm going to work on deploying one using kubernetes, using common helm charts and Amazon's new Open Distro Elasticsearch.    This will help out the qserv team and the jupyter investigations, which have logs you need to inspect all over the place!     "
Answer: 31774.0

User story: "Action from QAWG - to set up a group to look into needs for image display."
Answer: 50140.0

User story: "AS discussed at db-team Wed meeting it's time to start looking at NoSQL options for PPDB backends, several candidates were mentioned with Cassandra probably being most promising.    I'm going to study everything Cassandra and try to implement PPDB with it. We do not have a reasonable scale testing platform for it but I can do at leas a basic testing using either NCSA cluster or even my desktop."
Answer: 35966.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: 24885.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: 24884.0

User story: "Similar to DM-18176 but for May 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: 39125.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Add option to add regions to gen3 butler when ingesting raw images"
Answer: 10321.0

User story: "Repeat DM-19526 using LSST-produced coadds as templates.    Specifically,    - Using the same science images as DM-19526;  - Using LSST WarpCompare coadds as templates;  - Using A&L differencing, with decorrelation    demonstrate that you can recover raw DIASource counts comparable to those reported in DMTN-021."
Answer: 115223.0

User story: "Repeat DM-19525 using LSST-produced calexps.    Specifically,    - Using the same visits DM-19525, but with calexps generated through ap_pipe processing (rather than archivcal instals) as both template and science image;  - Using A&L differencing, with decorrelation    demonstrate that you can recover raw DIASource counts comparable to those reported in DMTN-021."
Answer: 125427.0

User story: "Repeat DM-19524 using HiTS data.    Specifically,  - Identify some HiTS data in the [ap_verify_ci_hits2015https://github.com/lsst/ap_verify_ci_hits2015] repository;  - Fetch instcals corresponding to that data from the DECam archive;  - Using those instcals as both template and science image;  - Using A&L differencing, with decorrelation    demonstrate that you can recover raw DIASource counts comparable to those reported in [DMTN-021|https://dmtn-021.lsst.io/]."
Answer: 115460.0

User story: "Repeat DM-19523 but add a decorrelation step, demonstrating we can repeat the results of DMTN-021.    Specifically,    - Given the L. Allen data described in DMTN-006;  - Using “instcal” data available from the DECam archive as both science and template image; and  - Using A&L differencing, with decorrelation    demonstrate that you can recover raw DIASource counts ~the same as recorded in DMTN-006."
Answer: 220230.0

User story: "Following DM-18632, we should be able to demonstrate that we are able to reproduce the DIASource counts given in [DMTN-006|https://dmtn-006.lsst.io].    Specifically,    - Given the L. Allen data described in DMTN-006;  - Using “instcal” data available from the DECam archive as both science and template image; and  - Using straightforward A&L differencing, with no decorrelation    demonstrate that you can recover raw DIASource counts ~the same as recorded in DMTN-006."
Answer: 220233.0

User story: "~ 2hrs of meetings/ week"
Answer: 276297.0

User story: "Summarise paper of interest to DM Science on transient processing    https://arxiv.org/abs/1904.05922"
Answer: 118664.0

User story: "I would be using this task to set up my development environment, Research the libraries I would need for fiberSpectrograph c++ code to be imported to python. Mostly R&D and setting up hardware. "
Answer: 24841.0

User story: "Following the pattern already established for standard coadds."
Answer: 20635.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: "Look at DCR corrected templates generated from a range of different seeing conditions.  Perform aperture photometry at a number of radii on detected sources.  Generate an aggregate statistic describing the extendedness of point sources.  (In particular, we are aiming to establish whether there is there a notable difference from the zero airmass case).  Generate similar plots with CompareWarp templates to provide a comparison."
Answer: 90806.0

User story: "Go through the SAL issues we currently have and identify which ones are high priority, low priority, and which we can delete."
Answer: 20254.0

User story: "This task will cover the effort going over the TMA Agenda which will include meetings with Shawn to go over and assist in any activities. Meeting with Sandrine to cover high level view of the TMA project that she has agreed to go over with me. And reading documentation with Tiago to gather knowledge and better assist in identifying what requirements we are missing or need from Tekniker. "
Answer: 18735.0

User story: "Downloaded control software from thorlabs which contains the libraries necessary for the .net framework. Followed their example for the MFF101 flipper to flip back and forth, setup .net framework using mono(a cross platform implementation of the .net framework). Flipper example would not compile because native c dll were only compatible with a windows c library."
Answer: 24780.0

User story: "Pull down the code from Docker hub and using their instructions build onto the Simulation Cluster."
Answer: 126778.0

User story: "Write a conda recipe that works for the ts_tunablelaser."
Answer: 24339.0

User story: "This task is to track the effort to update the SAL messaging tests.  I want to maintain the individual message testing, so updating the scripts that generate the tests will be somewhat tricky."
Answer: 36175.0

User story: "This task covers time needed to setup and configure the TSSW Jenkins environment.   * Install and run Docker on the host   * Get the ts_xml job configured and running"
Answer: 46076.0

User story: "My time has been requested to help prepare the team for the TMA workshop visit in June.  This task covers the time needed to attend meetings, read documentation and other efforts, as needed."
Answer: 40602.0

User story: "This task is to track the effort to update the SAL messaging tests.  I want to maintain the individual message testing, so updating the scripts that generate the tests will be somewhat tricky."
Answer: 36181.0

User story: "The FITS region files we are writing use LSST pixel 0,0 as origin.  This means that when the regions are loaded into DS9 the regions are shifted by a single pixel.  Adjust the output of the region to correct for this (and also adjust when reading back in)."
Answer: 303.0

User story: "All activities as the DM liaison to the DESC "
Answer: 277455.0

User story: "All activities as the DM liaison to the DESC "
Answer: 89059.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: "All activities as the DM liaison to Strong Lensing science collaboration    "
Answer: 55391.0

User story: "All activities as the DM liaison to the Solar System science collaborations. [~<USER> is the main liaison to the SSSC. "
Answer: 55397.0

User story: "All activities as the DM liaison to Galaxies science collaboration"
Answer: 277473.0

User story: "All activities as the DM liaison to the Active Galactic Nuclei Science Collaboration"
Answer: 169465.0

User story: "All activities as the DM liaison to the Stars, Milky Way, and Local Volume"
Answer: 169345.0

User story: "All activities as the DM liaison to the TVS science collaborations"
Answer: 55575.0

User story: "All activities as the DM liaison to the TVS science collaborations"
Answer: 169484.0

User story: "Need to finalize the scope of SODA's upcoming presentation at IVOA InterOp in Paris, and prepare the materials accordingly.   "
Answer: 36013.0

User story: After some slack discussion, [~<USER>, [~<USER>, and [~<USER> have all provided me with some suggestions about how to make refcats.    There are the DR2 .csv files on lsst-dev here: {{/project/shared/data/gaia_dr2/gaia_source/csv}}    and a Parquet version here: {{/project/shared/data/gaia_dr2/gaia_source.parquet}}    {{meas_algorithms}} has {{IngestIndexReferenceTask}}, which I've been told is very slow. [~<USER> suggested using {{fgcmOutputProduct._outputStandardStars}} from {{fgcmcal}}, but it does not handle proper motion or parallax or many of the other fields. I should run some simple tests to see just how slow the "standard" code is and make some guesses as to what might be necessary to speed it up. And similarly, compare it with [~<USER>'s code and decide whether we should just use something like that. As part of this, I should look at reading Parquet vs. CSV.
Answer: 15797.0

User story: "status.lsst.codes died.  Replace with a similar thing this time, but also plan to k8sify it."
Answer: 5544.0

User story: "This shall let the MTAOS to use the functions in WEP with the simulated PhoSim images. At this moment, only ComCam is supported. The integration with corner WFS will hold until the SIMS supports the obs_lsst."
Answer: 21441.0

User story: "This will evaluate the performance of InfluxDB with the SAL influxwriter on SSD, NVME, and spinning disk."
Answer: 17234.0

User story: "I will be in Chile for  personal travel. I will reomte work from recinto  and take the opportunity to check in with Jacques Sebag, Andres^2 and  Luis Coral and others. If I can get up to the summit I will. ."
Answer: 66328.0

User story: "Currently the schema reserves 8 characters for the instrument name. This is insufficient for many instruments. Change to 16."
Answer: 160.0

User story: "Submit RFC on exactly to define OTT1, as discussed at dm-sst meeting 2019-01-25.     At the SST meeting 2018-12-07, the SST proposed to define OTT1 as:     _*‘the last alert of the visit is made available to the stream’*_          "
Answer: 141008.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: "Resume preparations for incident monitoring and response, with a focus on near-term needs, e.g., Base Center online and Auxiliary Telescope on sky."
Answer: 4.0

User story: "Update Generic Camera CSC to be more ATCamera-like."
Answer: 146.0

User story: "The proposal here is to apply the same framework established in imgserv to build a standalone container image for metaserv, to be taken out of webserv container, which can then be deployed to lss-lsp-int and lsst-lsp-stable.    After this work, the webserv container, which built lsst_stack from source, can be retired from DAX."
Answer: 19520.0

User story: "This task is to make progress on the team documentation. We know we need in line documentation hosted to make out software documentation more accessible. "
Answer: 7160.0

User story: "starting ASC development, with a focus on the queue and command formatting/parsing code, which can be done with the information we have now. once we have a name for the ASC component.. something like MTOpticalAlignment, create a repo for it"
Answer: 149265.0

User story: "The chiller is set up in the lab with an N-Port ethernet-to-rs232 converter. Figure out how to get that talking to the whitelight CSC."
Answer: 8644.0

User story: This task it to build the pointing component for SAL 3,9 using the RPMs. Notice that I was already able to build it "the old way".
Answer: 667908.0

User story: "DM-17981 created a minimal heterogenous map that only supports single-key operations in C++ (but the full set of mapping operations in Python). Since our future persistence framework may be in C++, add a visitor system so that we can  let {{GenericMap}} instances be persisted."
Answer: 63611.0

User story: "Chiller and White Light CSCs were separated at some point in the past because they were going to be in different languages and written by different people. Now they're both python and I'm working on both. So we've decided to simplify them a single CSC rather than a pair of CSCs with a third CSC coordinating.    This task is to bring the currently-existing code for the chiller into the White Light CSC, merge their SAL topics, and get a docker environment up and running for the new unified CSC."
Answer: 31530.0

User story: "Add standalone dax_imgserv, and dax_metaserv docker builds to Jenkins CI, under the old webserv, as moniker.         As Josh suggested, this is to be done via a PR on lsst-sqre/jenkins-dm-jobs."
Answer: 17395.0

User story: There are loops like this that have a race condition as BlendScheduler::_schedulers can change.  {code:java}  for (auto const& sched : _schedulers) {      if (sched != nullptr) str += sched->chunkStatusStr() + "\n";  }{code}   _schedulers need mutex protection. Using a copy of the shared pointer instead of references may work but could have other side effects.     
Answer: 17296.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: "A recent discussion with [~<USER> relayed a comment from [~<USER> to the effect that at least some of the performance problems in reading afw.table files is due to a lot of time spent in {{malloc}}.  I have a guess at where that is happening - in the creation of {{shared_ptrs}} for all of the records - and if that's correct, an idea for how to possibly fix it without breaking anything (by allocating extra space for the Record object in the larger block allocated by the table that actually holds the data, and then using {{std::allocate_shared}} to avoid a heap allocation when constructing the shared pointer.    That still uses the same amount of total memory, so unless it reduces fragmentation in a subtle way, it's unlikely to address DM-15578 - and the existence of that issue makes me think there must be something else quite wasteful going on, even if I'm right that we could avoid some {{malloc}} calls with the proposal above.    [~<USER>, [~price], [~<USER>: if any of your recent profiling produced data that could confirm or reject this hypothesis, please let me know.  Otherwise I'll try to profile this myself and put together a fix if I'm right, but I'm afraid I can't put this at the top of my priority list right now.     "
Answer: 12870.0

User story: "We have old codes that run at NCSA for SAL 3.8.41. Those should be merged into one place. "
Answer: 8581.0

User story: "In the _SALSubsystems.xml_, the _Generics_ attribute should be converted from a boolean to a whitelist. This list is the generic commands and events that the CSC WILL support and implement. Only those items list here should be transitioned into the CSC API."
Answer: 310655.0

User story: "Because the architecture of scarlet has been completely redesigned, it is necessary to ensure that the new version is performing at least as well as the older version on simulations and visually (and in terms of a chi^2) on real HSC data. Once this has been confirmed the new version can be merged to master and updated in the LSST stack."
Answer: 331448.0

User story: "The DMSR has several composite requirements, e.g https://jira.lsstcorp.org/browse/LVV-61 and https://jira.lsstcorp.org/browse/LVV-62  that simply aggregate the child requirements.     We need to decide how to handle these for verification. Do we simply list the LVV of the child requirements for inspection and pass this LVV if all child LVV pass, or should  remove them from the DMSR? What was the original purpose of these composite requirements when the DMSR was written?"
Answer: 191769.0

User story: "DM-19384 found that there are fairly tight relations between the sizes & fluxes of single Sersic fits. This ticket is to test whether one can improve the initialization of fixed (e.g. exponential, de Vaucouleurs) and free-n multi-Gaussian Sersic fits given the parameters from another (typically faster Gaussian) fit."
Answer: 69183.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: "MultiProFit already has code for batch fitting of galaxies (DM-18707) but needs a script to automatically generate slurm job scripts to run on the verification cluster (or tiger)"
Answer: 54727.0

User story: "Implement [DALI-async|[http://www.ivoa.net/documents/DALI/20170412/PR-DALI-1.1-20170412.html]] for ImageServ.       Furthermore, it should implement the state machine as specified in Universal Worker Service (UWS): [http://www.ivoa.net/documents/UWS/20161024/REC-UWS-1.1-20161024.html]    This ticket also involves setting up and using celery as distributed task queue, and Redis for message broker and results backend, all within the imgserv container.  Besides Redis, celery can be configured for RabbitMQ, Beanstalk, MongoDB, CouchDB, databases via SQLAlchemy. Extending support to HTCondor  has been done, e.g. gwcelery (LIGO) for reference.    The celery worker allocates one Python process per CPU core, by default.     With this /async framework completed, it'll be trivial to implement /sync on top of it, hence de-coupling the flask frontend from the image processing backend (worker)."
Answer: 172738.0

User story: "- Examine how to extract the local (fixed) and spatial AL kernel solution as coefficients of the basis functions.   - Create an overview diagram that captures the implementation concept in the current C++ AL kernel solution ip_diffim code. Summarise the main role(s) of each class.   - Add a new section into the ip_diffim code notes and include the new diagram. Consider referring to or copy paragraphs from low-level code docstrings like psfMatchTask.py, etc.   - Add debug plotting for the coefficient visualization with possibly new lsstDebug config options."
Answer: 123894.0

User story: "With SAL 3.9 (actually 3.9.0-5) the generated maven projects contain a dependency on     <dependency>   <groupId>opensplice.dds</groupId>   <artifactId>dcpssaj</artifactId>   <version>6.9.0</version>   </dependency>    however that library/version does not exist in the ocs nexus repo:    !Screenshot from 2019-04-22 16-23-36.png!"
Answer: 215594.0

User story: "There was a review I did for Russell called slew scripts that would help me get up to speed on how docker containers work and how the team is using the scripting language. During the review I was having problems with getting my containers to get installed, I went through the process once on my centos machine, and again on my Mac. James also found a solution that solved the space problem that I was having on the cent os. This tasks is to cover the time spent on this effort. "
Answer: 24165.0

User story: "[~<USER> points out that our pybind11 eups package doesn't depend on numpy and astropy when in fact it technically should (and eigen as well I think)."
Answer: 167.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: "Something seems to be going wrong in the application of NQUARTER in visualizeVisit.py (maybe it's being applied twice, or maybe not at all).  [~<USER> suspects this was broken in DM-19371, and that the fix involves the new {{obeyNQuarter}} clause: [https://github.com/lsst/afw/commit/f154d3474b433e269d65c697c02cd1738e918942]"
Answer: 17299.0

User story: "Many region specifications (DS9, STC) define boxes in terms of center and width. Box2D has a {{getCenter()}} method but it would be useful if {{Box2I}} also had one to allow for more seamless usage."
Answer: 456.0

User story: "Jointcal depends on obs_cfht to enable some tests.  Precedent in the rest of the stack is to make all dependencies from algorithm packages on obs packages optional, with skip guards on the tests."
Answer: 1621.0

User story: "We're going to use hostPath to mount GPFS natively.  There's some cleanup we need to do to make this easy."
Answer: 221.0

User story: Services are currently invoked by going into the Python source code and invoking the service from there (ie, "python DMCS.py")  We should have shell scripts in the bin directory that invoke this.   Note that the source of those scripts will eventually be moved to bin.src, once we switch to using EUPS for the builds.   These are pretty simple one or two line scripts.
Answer: 93898.0

User story: "The build files for this package have hard-coded locations to some of the packages they link against.  This needs to be fixed to use environment variables which point at the root of those packages, so that the build files will work in different environments and/or when the locations of those packages changes."
Answer: 9860.0

User story: "The tests in the test directory need to be looked at in order to bring them up to DM standard testing.  Some of the tests require external services (Redis, RabbitMQ), and will only on systems that can access those services.  Those tests shouldn't be run  so that when the services aren't available."
Answer: 100956.0

User story: "The test_scripts directory contains Python scripts that are out of date for a variety of reasons.   Some expect configuration files to be loaded from hard coded directories in the source tree instead of $CTRL_IIP_DIR/etc/config, some use legacy code that may not be currently used, etc.  A general survey of what this code is intended to do."
Answer: 162760.0

User story: "DM-15862 broke y-band stray-light calibration lookup in Gen2 (which has always been a hack) by hard-coding a path, then deferring a fix for that to DM-16805.    That more complete fix will still have to wait for that ticket, but I'll try to get a fix for Gen2 only done here.     "
Answer: 688.0

User story: "prepare and present at the LSP review of the portal management status.    attend the 3 day review"
Answer: 1.0