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: "Once SQuaSH can access data from the Flask based API deployed in DM-12603,  we have to extend the Monitor app to allow visualization of metrics from different {{lsst.verify}} packages such as {{jointcal}}."
Answer: 66640.0

User story: "Create a flexible tile-based grid layout for www.lsst.io (LSST's documentation hub). Each tile corresponds to a different product (a document or software project). These tile grids will be used on index pages and let people browse different products in a category."
Answer: 1574.0

User story: "Update AST to the latest version, which adds support for writing SIP terms to FITS headers."
Answer: 1521.0

User story: "In DM-13163 we are changing the interface to {{ap_pipe}}.  This ticket is to write documentation in the {{docs}} directory for use with pipelines_lsst_io."
Answer: 215640.0

User story: "Because {{ap_pipe}} was developed with a CI verification workflow in mind (in concert with {{ap_verify}}), it includes ingestion and does not use the Stack primitives.  We are moving away from this approach; this ticket is refactor {{ap_pipe}} to have a separate ingestion routine as needed and to have the remaining processing be a {{CmdLineTask}}."
Answer: 112192.0

User story: "`processEimage.py` currently loads the metadata of a simulated observation twice and runs the same code both times, except it only provides a mapper the second time. This generates a warning the first time the code is run, and is unnecessary because the second call provides the correct exposure with VisitInfo."
Answer: 1342.0

User story: "See attached pdf for illustration and conclusion ![^molscat.pdf]"
Answer: 245296.0

User story: "When `obs_lsstSim` was updated in DM-12207 to reflect changes to photoCal, a typo resulted in the package crashing when run. "
Answer: 2807.0

User story: "The current settings for the color analysis plots are not ideal and sometimes misleading.  Please refine them to optimal and representative values."
Answer: 185898.0

User story: "Represent Alert Production in the Lossy Compression Working Group."
Answer: 40386.0

User story: "Create a notebook that enables convenient browsing of the static QA plots generated by the {{pipe_analysis}} scripts, in support of the QA analysis milestone."
Answer: 15103.0

User story: "Many of our current/futur reference stars don't have Stis-Calspec spectra  --> But maybe some theoretical template are already implemented in pysynphot  --> Installing it  --> Done"
Answer: 246406.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: "Here is a summary of the equivalent width measurement of O2 and PWV on Ronchi+order blocking filter images VS simulation :  (Illustrations are in the attached pdf)    1 ) PWV VS airmass has a stipper slope in simulation than in data (see slide 6).  Is it an actual overnight variation of PWV? Maybe. Could look if it's correlate wih HUMID keyword.    2 ) O2 EW is 30% smaller in simulation than in the data (see slide 6).    - This is not coming from the flux estimator, nor the aperture width (see slide 11 and 12).  - Lowering the resolution of the simulation to match the observations does not change the result (see slide 10).    Systematics :  - The barometric pressure in model templates at altitude 2.7km are smaller than reported keywords ~745 mb in highest model instead of 775 measured on site (see slide 7).   Changing the input model marginally shifts the O2 EW (I mean not significantly enough to account for the discrepancy between observation and simulation).  - The same measurement on Ronchi+ no filter images gives EWs 15% higher (see slide 9).     - The sigma of the fitted spectrum profile  shows a ~5% dip (on order blocking images) or a bump (on no filter images) at the location  of O2 line (see slide 8).     i-  This is not due to a fortuitous contamination from a nearby object,   ii - This is not a feature in the wings of the profile,  iii - This is not a feature in the stellar SED.     —> This is intriguing...    Note :  Strong reflection (see ds9 frame on slide 8).       I will move on to the Rayleigh scattering determination from Ronchi + no filter images.  "
Answer: 252346.0

User story: "[~<USER> writes:  {quote}  I have reviewed CCD defects set in the current  obs_subaru, and updated them.   The compiled defectRegistry and relevant files are uploaded as:     https://www.adc.nao.ac.jp/people/~furusawa/hsc/s18a/defects/defects_20171228.tar.gz    - Here, I tried to mask edge pixels of each CCD as we discussed in the  telecon (see the attached figure; red boxes are edge masks),   - and also masked out bad pixel clusters more carefully.   - I took a conservative choice for bad amps, in the same  manner as before, e.g., ccd=0 ch=0, ccd=43 cch=4, where I applied   masks for the entire amp, without too much tuning up the masked areas  and period.   - Similarly, I have masked ccd=94 ch=2 for all periods, as this amp  shows flat field error due to poor linearity correction with low-count  levels.    I am esting singleFrameDriver through coadding with these masks  over the RC dataset, and will report you when I found something bad.  But, in the meantime, I would be grateful if you could be prepared to   update the defects for the next release cutout.  {quote}"
Answer: 37468.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: "LTD Dasher trims document handles from titles to protect from cases where the document handle was accidentally inserted into the document title string. But for test reports, the title legitimately includes a document handle (but for a different document). See https://dmtr-53.lsst.io/v/index.html The fix is to only trim the document's own handle from a title (and only if it occurs as a distinct word unit)."
Answer: 81.0

User story: "Non regression on Qserv performances"
Answer: 86353.0

User story: Change the main edition tracking mode in LTD Keeper for LDM/DMTR/DMTN/SQR documents that have adopted the new document release workflow (https://developer.lsst.io/docs/change-controlled-docs.html).    See https://ltd-keeper.lsst.io/editions.html#tracking-modes    {code}  http --auth $TOKEN: patch https://keeper.lsst.codes/editions/<id> mode="lsst_doc"  {code}    Also exercise DM-13132 to delete the {{draft}} editions of those documents.
Answer: 70401.0

User story: "Sqrbot is getting a null response when inquiring about a Jira link."
Answer: 234.0

User story: "Provide engineering assistance to the LDM-294 maintainers to fix build issues and address technical debt."
Answer: 11322.0

User story: "Running libradtran simulation with CTIO altitude, no ozone,  and some not-so-clear-yet default parameters against observations.    Varying the airmass and the mm of PWV, then looking at two EWs :  O2 @ 765 nm  PWV between [880, 1040] nm.  !obsVSsimu0.png|thumbnail!  !obsVSsimu.png|thumbnail!    To do :  - Learn how to vary O2 content in libradtran simulation  - Replicate the analysis after downgrading the resolution of the simulated curve.  - Look at ozone and Rayleigh scattering using ronchi+no filter spectra."
Answer: 256310.0

User story: During the DM-503-3 processing, we encountered an error for HiTS dataId visit 411657, ccd 47, filter='g':    {code}  File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/  Linux64/meas_algorithms/14.0-7-g23fdbe95+15/python/lsst/meas/algorithms/  measureApCorr.py", line 251, in run      (name, len(subset2), self.config.minDegreesOfFreedom+1))  RuntimeError: Unable to measure aperture correction for required algorithm  'base_PsfFlux': only 0 sources, but require at least 2.  {code}    Further investigation shows that 6 PSF sources are selected, but all have self.refFluxKeys.flag set, so they raise the error above in {{measureApCorr}}.     This ticket is to investigate the root cause of the failure to select usable PSF sources.
Answer: 477827.0

User story: "Robert's input #10, DM-7321    Killing the firefly display window seems to leave the notebook that's talking to it perfectly happy, but it doesn't respawn the window even if I call the constructor again."
Answer: 633754.0

User story: "Robert's input #9, DM-7321    disp.pan(0, 0) is ignored (I think anything below (0.5, 0.5) fails). I'd expect to be able to pan any point to the centre of the display, but I'd certainly expect that it'd clip to a valid coord not silently ignore my request)"
Answer: 558574.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: "From Robert's input #13 in DM-8409:      Colours for masks appear to be case sensitive (unlike at least most web standards), and illegal colours such as RED are silently ignored *(#13)* "
Answer: 1267380.0

User story: "From Robert's input #7 in DM-8409:    Pixel coords are off by (0.5, 0.5) – the middle of the bottom left pixel should be (0, 0) (i.e. offset by (1, 1) from the fits standard, which assumes fortran-style 1-indexed arrays) *(#7)*  "
Answer: 308305.0

User story: "When I visit http://doxygen.lsst.codes/stack/doxygen/x_masterDoxyDoc/index.html, type something into the search box, and hit enter, I get a {{search.php}} file to download in response.    Obviously, I should get search results.    This was discussed on DM-10544, but doesn't seem to have actually been fixed there (or, if it was, it has subsequently broken again)."
Answer: 87760.0

User story: "The verification framework adds metadata associated with measurements in the Job object created by {{lsst.verify}}. Dispatch verify enrich that with provenance information obtained from the execution enviroment. While the former is arbitrary the later is mainly fixed and required by SQuaSH, thus we propose to separate them.    This will allow SQuaSH to support multiple execution environments as described in https://sqr-009.lsst.io/"
Answer: 20226.0

User story: "Atmospheric radiative transfer shows that :  - Rayleigh scattering follow a lambda**(-4) law -> No need to simulate it, direct fit is just fine.  - Ozone is localized in Huguens Band and Chapuis Band -> I'll try to adjust that on our data  !ozone.png|thumbnail!  - Water can be determined from EW measurements -> I'll extract the 2 accessible EW on the data.  !water.png|thumbnail!"
Answer: 262073.0

User story: "Attendance and involvement with Pathfinder Integration Activity #4b and associated meetings/workshops."
Answer: 27482.0

User story: "Attendance and involvement with Pathfinder Integration Activity #4b and associated meetings."
Answer: 296.0

User story: "The strict monotonicity projection using only the nearest neighbor creates fractal-like unphysical features and affects the accuracy of the deblender. This ticket is to implement a strict, weighted monotonicity projection similar to the weighted monotonicity operator that calculates the radial gradient.    For speed, this will have to be written in C++."
Answer: 39414.0

User story: "- Set up a more flexible environment to use the development DESDM software and a newer stack version  - Try the mini tests in lsst-dm/prod_wcl/wcl with stack {{w_2017_50}} and DESDM post-DM-12983,DM-12966 fixes.  - Make new configs, schemas, skymaps for w_2017_50 needed for the mini tests.  - Don't merge anything to {{prod_wcl}} as python 3 and other tests continue to be rely on the w_2017_33 version"
Answer: 1047.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: "www.lsst.io (DocHub) will be a portal for LSST project documentation, software projects, and other forms of information. This ticket is to create the Flask project for building out the www.lsst.io site, and outputting the Flask site as a static site deployed through LSST the Docs."
Answer: 21179.0

User story: "The UI element is ready in portal, we need to make the connection to user's file workspace from portal (when the workspace is available), make the necessary UI changes, implement API after DM-10854 is done.   - allow user to save files into the workspace   ** save image as FITS   ** save table in the proper format   - allow user to access the files in the workspace from portal,   ** upload file to do multiple position searches,   ** upload an image or table"
Answer: 836702.0

User story: "When running {{ingestImages.py}} on compressed ({{fpack}}-ed) images, the code explicitly looks in {{hdu=0}} which is the primary header which has no useful information. We need to use the default behaviour (go to the first HDU if it's compressed)."
Answer: 21454.0

User story: "This is the initial provisioning plan"
Answer: 141161.0

User story: "We want to run different branches of {{validate_drp}}.  We don't need to reduce the data twice, so we need to split the processing from the validation."
Answer: 46101.0

User story: "The NCSA security team evaluated and demonstrated authentication and authorization services in  https://jira.lsstcorp.org/browse/DM-3838 .  In this story we study the configurations that they  have setup on a test server at NCSA, and examine the approaches for suitability to support  the initial intersite file transfers associated with Spectrograph support. We focus on Kerberos/LDAP and Oauth2 described in https://jira.lsstcorp.org/browse/DM-4671 and https://jira.lsstcorp.org/browse/DM-4744 .  Finally we work with sysadmins at NCSA  to adapt  the 'one-off' configuration of the demo machine to a systematic and reproducible configuration with puppet modules. "
Answer: 18934.0

User story: "Delete the https://ldm-129.lsst.io site since it is now being maintained as a Word document entirely through DocuShare."
Answer: 8924.0

User story: "Radiative Transfer simulation can be performed either from ModTran or LibRadTran.    Here are simple instructions to install the later on MacOs Sierra :    sudo tar -xvf gcc-5.1-bin.tar.gz -C /.  sudo tar -xvf gfortran-5.1-bin.tar.gz -C /.    Then install libRadTran.    I have failed on all other methods.      "
Answer: 263725.0

User story: "Add a calculation of atmospheric refraction and utilities for differential refraction to the stack. These calculations are needed for the DCR-corrected templates that are being written in DM-9615, but they can be made more general and separated from the rest of the DCR code."
Answer: 11551.0

User story: "Fonts are missing from the PyPI distribution of lsst_dd_rtd_theme (for technotes) v0.2.0"
Answer: 266.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 goal is to address miscellaneous problems related to running DESDM packages under Python 3. This is a "bucket story" to capture the work of multiple staff members testing, debugging, and performing comparison runs.
Answer: 63343.0

User story: "Today I visited Sylvie Dagoret-Campagne at LAL to discuss the extraction of atmospheric parameters from spectra in a time series (Bouguer Line Method).    The method is needed when proper telescope calibration is unavailable.  This is the case for our ronchi+order blocking filter images needed to measure PWV.  Here is the calibration :  !r-calib.png|thumbnail!    As a result of this bad calibration, the atmospheric transmission is inaccurate :  !tatmodeco.png|thumbnail!    The Bouguer line method alleviates the requirement on an accurate telescope calibration (of course a stable instrumental response is mandatory).    I shall post Bouguer lines once they are produced, and then, will try to reproduce them with a radiative transfer simulation.    "
Answer: 265197.0

User story: "There is a considerable amount of work on the {{draft}} and {{DM-7501}} branches for LDM-294 that has been quiescent since October.  It includes updates to management staffing, e.g., Simon's move to Tucson.    There is also a apparent shortcoming of the Makefile for the document that means that the {{productlist.csv}} file is not used automatically to create all the required new .tex files as part of the build.  In particular, this affects the component/product table in Appendix A.    Finally, at the same time we should switch to the new conventions for release of change-controlled DM documents.    There are also further changes that could/should be made to the document, but this ticket is just about bringing old in-process work to a conclusion."
Answer: 81846.0

User story: "Do a column wise comparison of test catalogues to assess effects of quantisastion."
Answer: 190920.0

User story: "There are non-trivial aws region to region bandwidth charges on this months bill.  I presume this is a consequence of the s3 bucket used for git-lfs object being in us-west-2 while the jenkins instances are all running is us-east-1 (the plan was to move most everything to us-west-2 but it never seems to be a convenient time to do it when the annual reserved instances expire).  This traffic has greatly increased now that we are deleting the jenkins {{validate_drp}} job workspace(s) before each build.    Intra-aws-region bandwidth is free, so replicating all the git-lfs objects to a bucket in the us-east-1 region and running a second git-lfs server instance will eliminate these costs."
Answer: 129226.0

User story: the unit test failure is   {{core/modules/wsched/testSchedulers.cc(863): error: in "SchedulerSuite/BlendScheduleQueryBootTaskTest": check queryStats->getTasksBooted() == 1 has failed}}  
Answer: 40337.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 is very useful for qa/debugging to know which band was used as the reference band for the measurements in forced photometry on the coadds.  These are currently only persisted in the *deepCoadd_ref* output file, so will need to read these in and add the appropriate columns to the parquet tables."
Answer: 10329.0

User story: "Create a new HSC beta release with the following:  * DM-12979: y-band background subtraction  * DM-12968: Include INTERP+CR pixels in coadds  * DM-12985: Bad masking and interpolation around bleeds  * DM-13082: test failure due to DM-12968 config move    Will try to avoid pulling over DM-12764 (Overhaul SkyWcs) and related fall-out."
Answer: 320.0

User story: "Create a new folder {{/datasets/hsc/calib/20171219/STRAY_LIGHT}} and copy the data from Paul's folder /scratch/pprice/strayLight     Create a link in {{/datasets/hsc/calib/20170105/STRAY_LIGHT}}     Check {{yBackground}} are available via Butler. "
Answer: 41868.0

User story: "1) make Hub and Lab aware of their external endpoint  2) make it easy to switch back and forth between CILogon and GitHub for OAuth2"
Answer: 335.0

User story: "Attached is the output of the photometric pipeline.  This is the catalog of the targeted standard stars with their associated observed flux.    Here is an illustration :  !hz2.png|thumbnail!    The flux estimator is SEXtractor ISOCORR variable, this is a gaussian extrapolation of the PSF.  This is favored over aperture flux to alleviate the seeing dependency over the flux estimator :  See !normalizedfluxVSaperture.png|thumbnail!  This shows that ISOcorr is an acceptable proxy for aperture flux at infinite radius."
Answer: 266653.0

User story: "Update LDM-503 to include approriate tests for handling data from Camera Calibration Optical Bench (CCOB). This may only be possible after the Feb meeting which sets the CCOB schedule. "
Answer: 175242.0

User story: "Informally we agree to handle data coming from Camera Calibration Optical Bench (CCOB) as part of early integration. To make this more formal we need to  place a requirement on DM, in LSE-61 to be capable of archiving, and performing a meaningful processing on, data from Camera I&T data collection on the CCOB.  "
Answer: 133954.0

User story: """xterm"" doesn't work, but ""xterm-color"" does."
Answer: 28.0

User story: "When Lander fails to upload a PDF at the end of a build, the build is still marked as a success (see, e.g., https://travis-ci.org/lsst/LDM-534/builds/318277471). That's confusing — please can we change this so the failure is acknowledged?"
Answer: 83513.0

User story: " Including availability, capacity & incident response based on service monitoring capabilities"
Answer: 25752.0

User story: "Reprocess the HSC RC1 dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], using Stack w_2018_02.  Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (DM-10129/DM-11020)."
Answer: 43031.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: "Relocate and refactor the new TAN SIP fitter from meas_astrom to afw to allow it to be used to write TAN SIP approximations to more general WCSs.  "
Answer: 357045.0

User story: "See attached gitter convo"
Answer: 4482.0

User story: "{{Dataset}} and {{Quantum}} have compound primary keys ({{id, registry_id}}) of which we'd like the {{id}} to be {{autoincrement}}. Unfortunately that is not possible with {{sqlite}}. So currently we hack around that by setting the {{id}} in code. This is flaky (gets reset between instances currently, but this can be fixed) and ugly. Find a better solution (or implement the current solution more robustly)."
Answer: 233285.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: "Jointcal is still getting NaNs in some of the HSC PDR1 data. It appears that finite errors are not guaranteed by the centroid_flag, so we have to reject non-finite Sigmas during source selection. For now, we'll add it to astrometrySourceSelector, but we'll have to think of a better solution since this will affect all source selectors."
Answer: 4267.0

User story: "[~<USER>'s work on color terms in u/fix_outliers should help improve the photometry models.    This ticket is to port over [~<USER>'s work in the u/fix_outliers branch (specifically this commit: https://github.com/lsst/jointcal/commit/e1d0292c71275315a6b17b67ecaf47acd2ffbee8 ) to use {{ReferenceSourceSelectorTask}}, add a unittest to demonstrate that the color terms do affect the fit (for both the simple, and constrained models), and update the other tests to reflect any changes in the fit metrics."
Answer: 604949.0

User story: "[~<USER>'s work on selecting reference sources by S/N and magnitude might help improve the refcat that jointcal uses. But [~price] made a {{ReferenceSourceSelectorTask}} that we can configure for this purpose, instead of having code internal to jointcal.    This ticket is to convert [~<USER>'s work in the u/fix_outliers branch (specifically this commit: https://github.com/lsst/jointcal/commit/e8393ac2e21117c15458156423445b19f75b503a ) to use {{ReferenceSourceSelectorTask}}, add a unittest to demonstrate that it does affect the fit, and update the other tests to reflect any changes in the fit metrics."
Answer: 633536.0

User story: "Update the existing technote theme ({{lsst-dd-rtd-theme}}) to include the LTD edition switcher (already featured on pipelines.lsst.io and developer.lsst.io) and include the Edit on GitHub button.    Update Documenteer to pull down the new theme."
Answer: 5897.0

User story: "Minor improvements to UX"
Answer: 184.0

User story: "The following build failed on OSX but succeeded for all Centos builds:    https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/27194/pipeline/    Given that the code in this commit doesn't touch C++, let alone meas_base, this is highly likely to be a random/non-deterministic failure, so debugging might be worthwhile to start reducing the frequency with which these happen."
Answer: 4488.0

User story: "Before updating the stack API (DM-12404) and testing the deblender on HSC data (DM-11330), we should make sure that the new version works on the same simulated data as well or better than the previous version."
Answer: 50364.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 purpose of last Chile observations is to assess the Calspec radiometric standards from ground  based synthetic photometry.  This means two distincts set of observations :  - Broadband observations of Calspec standards,  - Real time monitoring of atmospheric transparency  from low-resolution spectrometry of targets with known SED + telescope throughput calibration from artificial light sources.    The ongoing task is to reduce both set of observations and to produce the subsequent analysis. "
Answer: 272603.0

User story: "Running {{ap_verify}} on a dataset of any reasonable size requires parallelization on the verification cluster via SLURM.  We also may wish {{ap_pipe}} to support {{-j}} parallization in the future.  However, the existing code writes all metrics to the same filename before moving them away, so parallel runs clobber each others' metrics.    This ticket is to implement an alternate scheme for persisting metrics that is threadsafe."
Answer: 148290.0

User story: "Ideally, we should be using db for all expression evaluation on the server side and remove all references to Expressions.java. We'll still keep Expression.js on client side for user-friendly column expression validation.    This is a ticket for column expression issues not covered by the related tickets.    - Expand the list of functions that can be used in Expression.js to include JDBC and Foundation functions, supported by HSQL, see http://hsqldb.org/doc/guide/builtinfunctions-chapt.html"
Answer: 1352476.0

User story: "Examples of the functions we might want to implement as custom db functions:    lg(x) - same as log10,  if(booleanExpr, expr1, expr2)   "
Answer: 1352499.0

User story: Support quoted non alpha-numeric column names in column expressions.    Currently, we only support column expressions for the columns that contain letters, digits, and underscore.     NED tables contain column names that are not alpha-numeric ("RA(deg)", "Redshift Points"). Expressions will fail on these columns.     Since we have no control on how columns are named in non IPACTable tables, we should be able to support any kind of column name or produce a warning if we can not support it.    
Answer: 148369.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: "Use database expressions in DecimationProcessor and the related code. (Currently we are using Expression.java library to obtain column expression values when producing decimation (heatmap) data.    Since we are using database expressions for filtering, we need to make sure the same expressions are used to produce the data.    Ideally, we should be using db for all expression evaluation on the server side and remove all references to Expressions.java.  We'll still keep Expression.js on client side for user-friendly column expression validation.    Currently server-side expression library is used in:  DecimationProcessor.java  QueryUtil.java (doDecimation)  IpacTablePartProcessor.java (deprecated getDataFile - decimation)  HistogramProcessor.java (old single-trace charts)  XYGenericProcessor.java (old single-trace charts)    "
Answer: 1352520.0

User story: "First prototype."
Answer: 240240.0

User story: "Perform overall facility planning and high-level engineering. This typically includes emergent work at the management, steering and planning level."
Answer: 184074.0

User story: "Perform overall facility planning and high-level engineering. This typically includes emergent work at the management, steering and planning level."
Answer: 97647.0

User story: "Perform overall facility planning and high-level engineering. This typically includes emergent work at the management, steering and planning level."
Answer: 130944.0

User story: "Currently, one needs a modtran installation to build the atmosphere model for FGCM and compute the look-up-tables (that depend on the atmosphere + instrument).  A recent conversation made me realize that I can compactly pre-compute sets of atmospheres for various sites/elevations that can be distributed with FGCM.  This will make the code more portable and flexible for use with LSST to swap out different instrument models."
Answer: 41962.0

User story: "sqr-018 needs some maintenance"
Answer: 7151.0

User story: In this case "production" means passed very friendly early user testing and the system is ready for integration and testing at the service level.
Answer: 243451.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 address the problems observed in detection efficiency in HSC, we'd like try the following modifications to either SourceDetectionTask or DetectCoaddSources (since this only needs to happen on coadds):    # Do not rescale the coadd variance plane.  # Start with a preliminary detection step with an aggressive threshold (2-4 sigma) to identify regions that may contain objects.  Grow these footprints as usual.  # Run background estimation, ignoring the just-detected footprints as usual.  # Add a temporary set of sky objects and measure PSF fluxes on them.  # Use the ratio of the empirical RMS ("rms") of the sky object flux to the mean of its quoted uncertainty ("err") to determine an "effective" threshold for final detection from the configured ("nominal") threshold: effective = nominal*err/rms.  # Proceed with normal detection as it currently exists in SourceDetectionTask, discarding the temporary sky objects.    We may also be able to use the mean of the sky object flux to determine the correction to the background, instead of running background estimation instep (3) before adding the sky objects.  This should be possible via a config option - we don't know whether the finite number sky objects will give us sufficient S/N to estimate the background, and we also don't know if subtracting the background after a more aggressive detection step will yield a mean sky object flux that is consistent with zero.    In testing, we'll need to tune the threshold for the first aggressive detection phase and test that the final "reEstimateBackground" step in SourceDetectionTask doesn't degrade the quality of the background (by looking at the regular sky objects added later).    Removing the coadd variance scaling will also change the reported uncertainties for our measurements.  I think the reported uncertainties were already wrong, but this may make them slightly more wrong.  We could consider scaling all of the uncertainties by (rms/err) in a manner similar to how we apply the aperture corrections, which should push them closer to being correct (it would only be exact for PSF fluxes on faint point sources, I think).  But we should at least make sure that (rms/err) is recorded for each patch so we could let the science users apply that factor if applied.    [~<USER>, please check that all of the above makes sense to you (using another background estimation step instead of sky objects to correct for the mean offset was Tanaka-san's idea; I think it's worth trying both approaches).  At the HSC telecon on 12/12 we agreed that [~price] would try to implement this after getting the y-band background subtraction in.
Answer: 63434.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: "Until obscore/SIA_v2 is ready for use, imgserv is staying put to get the necessary metadata for images directly from the db. The work is done here to streamline that db access in imgserv today.           Was:    The scope of work for this feature is much larger than initial projection after investigation.  metaserv_v1 needs to add facility to convert query results into a JSON response.  imgserv_v1 will then need to convert the JSON response into a Python object suitable for input into afw functions for FITS metadata handling.  ----  In dax_imgserv_v1, a module metaservGet is currently containing a SQL call to retrieve metadata for nearest image based on RaDec. This functionality should   be provided by dax_metaserv API as a basic use case.    This ticket is for investigating the scope of this work.    ------------------------------------------------------------------------------------------------------------------------"
Answer: 205872.0

User story: "Add the new table to PDAC catalog search panel  Search and display the the results properly"
Answer: 12907.0

User story: "confirm  that the newly loaded NEOWISE data table is accessible through current DAX service"
Answer: 1776.0

User story: "Right now there is a porting branch for the {{verify}} changes.  This needs to be merged back to master.  First, we need to show that the two branches are producing the same thing.  I'd like to do this by publishing to two different deploys of SQuASH, but we could do it by simply inspecting the two JSON files."
Answer: 341279.0

User story: "backup file lists are occasionally empty. Find and fix issue."
Answer: 2.0

User story: Reprocess the HSC RC dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], using Stack w_2017_52.  Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (DM-10129/DM-11020).    (Due to the holiday season, w_2017_52 may not be available, in which case we'll make this ticket "Won't Fix" and move on to 2018.) 
Answer: 73849.0

User story: "The updated deblender does not have useful docstrings, so to assist with DM-12404 (and make sure that I understand the new API) I am writing docstrings for all of the new classes and methods."
Answer: 8767.0

User story: "This ticket implements RFC-421.    {{display_firefly}} will be added as {{setupRequired}} to the table file in {{lsst_distrib}}."
Answer: 220.0

User story: "HSC has had some features in the y-band images due to encoders in the instrument. [~<USER> has written some code to remove them (report and link to the code [here|https://hscdata.mtk.nao.ac.jp/hsc_bin_dist/4fc0f523/]), and we would like to include it in the pipeline."
Answer: 9326.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "[~<USER> saw a similar failure yesterday buiding {{firefly}}.  I have confirmed that {{devtoolset-6}} is still present in the container used to run {{validate_drp}} and the base container has not changed since the start of the month.    {code:java}  $ docker run -ti lsstsqre/centos:7-stack-lsst_distrib-d_2017_12_11 gcc --version  gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)  Copyright (C) 2015 Free Software Foundation, Inc.  This is free software; see the source for copying conditions.  There is NO  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.    $  docker run -ti lsstsqre/centos:7-stack-lsst_distrib-d_2017_12_11   [lsst@7feae47025be stack]$ gcc --version  gcc (GCC) 6.3.1 20170216 (Red Hat 6.3.1-3)  Copyright (C) 2016 Free Software Foundation, Inc.  This is free software; see the source for copying conditions.  There is NO  warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  {code}    {code:java}  [validate_drp] Running shell script  JENKINS-33510: working directory will be /home/jenkins-slave/workspace/sqre/validate_drp/hsc not /home/jenkins-slave/workspace/sqre/validate_drp/hsc/validate_drp  + cd /home/jenkins-slave/workspace/sqre/validate_drp/hsc/validate_drp  ++ set +o  + SHOPTS='set +o allexport  set -o braceexpand  set +o emacs  set -o errexit  set +o errtrace  set +o functrace  set -o hashall  set +o histexpand  set +o history  set +o ignoreeof  set -o interactive-comments  set +o keyword  set +o monitor  set +o noclobber  set +o noexec  set +o noglob  set +o nolog  set +o notify  set +o nounset  set +o onecmd  set +o physical  set +o pipefail  set -o posix  set +o privileged  set +o verbose  set +o vi  set -o xtrace'  + set +o xtrace  Creating user data directory: /home/jenkins-slave/workspace/sqre/validate_drp/hsc/home/.eups_userdata  + scons  scons: Reading SConscript files ...  EUPS integration: enabled  Checking who built the CC compiler...gcc=4.8.5  CC is gcc version 4.8.5  Checking for C++14 support  Checking whether the C++ compiler works... no  C++14 extensions could not be enabled for compiler 'gcc'  script returned exit code 1  {code}  "
Answer: 4465.0

User story: "Planning, management, status tracking, architecture, T/CAM & DMLT activities, etc."
Answer: 13194.0

User story: "Add logging to LSST the Docs Keeper to enable basic monitoring of the service. Use structlog (http://www.structlog.org/en/stable/) to get JSON-formatted log messages that can be easily parsed by ELK or Stackdriver. Logs will go to stdout so that any log shipper can get them."
Answer: 2978.0

User story: "The python api needs to support HiPS like the JavaScript API"
Answer: 194342.0

User story: "[~<USER> has been writing up a paper based on the new deblender. For my part I will help write some sections of the paper, including results from tests on both HSC and Sim data."
Answer: 54370.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: "Do the following:    * make all text draw with canvas, removed div text drawing.   * make restore button work with HiPS  * fix: color dialog now aware of HiPS  * firefly server can act as hips proxy - hips images are brought to firefly server first  * change hips cache to 100 images  * add hips to firefly Api   * give more level of hips zoom depth  * allow HiPS to save to png"
Answer: 15755.0

User story: "DocuShare moved from docushare.lsstcorp.org to docushare.lsst.org. The Lander project validates links to DocuShare, hence it needs to be updated with the new URL."
Answer: 69.0

User story: "This ticket covers effort associated with configuring LDM and DMTR (LaTeX documents) for deployment on LSST the Docs."
Answer: 93572.0

User story: "I think we agreed at the 2018-12-11 Monday Meeting that it's better to included interpolated CR pixels in the coadd (since the interpolation is pretty good) rather than leave them out and get lots more pixels masked with INEXACT_PSF.    [~price], if you're in a position to do this quickly before the next HSC release, please steal it.  Otherwise I'll try to get to it later."
Answer: 11123.0

User story: "Container builds no longer work; need to scl enable devtoolset-6"
Answer: 59.0

User story: We need a squash API acceptance test suite that can be run against the SQuaSH test client implemented on DM-9741 that exercises the the entire REST API.    It should use for example "real world" fixture data include the large (>50MiB) HSC measurement data set.     
Answer: 26334.0

User story: "need to fit a continuum on all the ronchi+order_blocking_filter images before extracting EW."
Answer: 277964.0

User story: "The current archive from a stack-os-matrix job looks like:    {code:java}  archive/  └── lsstsw      └── build          ├── afw          │   ├── _build.log          │   ├── config.log          │   └── tests  {code}    This is likely the result of each parallel branch that finishes stomping on any prior results.  The end result is an probably a mess of overwritten artifact files names and an aggregation of (unique) file names from different build configurations."
Answer: 1395.0

User story: "[~<USER> ran {{clang-tidy}}'s static code analysis tools on jointcal, and saved the results in a new user branch:    https://github.com/lsst/jointcal/pull/62    We should merge these automatic cleanups into jointcal master, by pulling them into a branch for this ticket."
Answer: 1309225.0

User story: "As the top level CI driver script {{jenkins_wrapper.sh}} is now checking compiler strings, these first line CI jobs need to always run on nodes with either the {{osx-10.11}} or {{osx-10.12}} label so an exact compiler string can be specified.  Prior to this, the more generic {{osx}} label was being used which includes all {{osx-10.1[12]}} nodes.  This cuts the effective number of available OSX nodes in half.  Multiple compiler strings, wildcard matching, or both should be implemented."
Answer: 121021.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: "{{ldf_ops_tools}} is a set of operator tools for running LSST codes via the DESDM framework. The goal is to port it to Python 3."
Answer: 18851.0

User story: "{{desdmfw_drp_appintg}} is a set of operator tools for running LSST codes via the DESDM framework. The goal is to port it to Python 3."
Answer: 18854.0

User story: "{{desdmfw_lsst_plugins}} is a set of operator tools for running LSST codes via the DESDM framework. The goal is to port it to Python 3."
Answer: 18857.0

User story: "Federica Bianco (Science Collaborations chair) requests a new private category on https://community.lsst.org that will enable members of Science Collaborations to review telecon notes and discuss outcomes."
Answer: 5.0

User story: "Update the [Documenting Python APIs|https://developer.lsst.io/docs/py_docs.html] page in the DM         Developer Guide to clarify and document issues that have come up in real-world application of Numpydoc-based docstrings in the last few months. This ticket encompasses the issues DM-12926 and DM-12936."
Answer: 21272.0

User story: "We are going to use Kubernetes for LSP deployment as a whole. We need to experiment with K8s for SUIT/Firefly deployment. "
Answer: 91955.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: Mineo-san writes in [HSC-1425|https://hsc-jira.astro.princeton.edu/jira/browse/HSC-1425]:    When I try to construct flat with hscPipe version 6.0-beta2 by:  {code}  constructFlat.py $PWD --rerun=testflat --batch-type=smp --cores=17 --id field=DOMEFLAT ccd=49 filter=HSC-Y --config isr.doBias=False isr.doDark=False  {code}  the command fails with the following error message:  {code}  flat INFO: Scatter combination  flat INFO: Combining {'ccd': 49, 'filter': 'HSC-Y', 'calibDate': '2014-03-25'} on alize.mtk.nao.ac.jp:31558  flat.combination INFO: alize.mtk.nao.ac.jp:31558: Measured background of stack is 0.999997; adjusting to 1.000000  application called MPI_Abort(MPI_COMM_WORLD, 1) - process 0     Traceback (most recent call last):    File "/data2/hscpipe/6.0-beta2/stack_6.0-beta2/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0b1-hsc+6/python/lsst/ctrl/pool/pool.py", line 113, in wrapper      return func(*args, **kwargs)    File "/data2/hscpipe/6.0-beta2/stack_6.0-beta2/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0b1-hsc+6/python/lsst/ctrl/pool/pool.py", line 237, in wrapper      return func(*args, **kwargs)    File "/data2/hscpipe/6.0-beta2/stack_6.0-beta2/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0b1-hsc+6/python/lsst/ctrl/pool/pool.py", line 713, in reduce      *args, **kwargs)    File "/data2/hscpipe/6.0-beta2/stack_6.0-beta2/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0b1-hsc+6/python/lsst/ctrl/pool/pool.py", line 570, in _reduceQueue      resultList = [func(self._getCache(context, i), data, *args, **kwargs) for i, data in queue]    File "/data2/hscpipe/6.0-beta2/stack_6.0-beta2/stack/miniconda3-4.3.21-10a4fa6/Linux64/ctrl_pool/6.0b1-hsc+6/python/lsst/ctrl/pool/pool.py", line 570, in <listcomp>      resultList = [func(self._getCache(context, i), data, *args, **kwargs) for i, data in queue]    File "/data2/hscpipe/6.0-beta2/stack_6.0-beta2/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_drivers/6.0b2-hsc/python/lsst/pipe/drivers/constructCalibs.py", line 731, in combine      finalScale=struct.scales.ccdScale)    File "/data2/hscpipe/6.0-beta2/stack_6.0-beta2/stack/miniconda3-4.3.21-10a4fa6/Linux64/obs_subaru/6.0b1-hsc+6/python/lsst/obs/hsc/calibs.py", line 48, in run      self.maskVignetting(mi.getMask(), detector)    File "/data2/hscpipe/6.0-beta2/stack_6.0-beta2/stack/miniconda3-4.3.21-10a4fa6/Linux64/obs_subaru/6.0b1-hsc+6/python/lsst/obs/hsc/calibs.py", line 63, in maskVignetting      transform = detector.getTransformMap().get(detector.makeCameraSys(afwcg.FOCAL_PLANE))  AttributeError: 'lsst.afw.cameraGeom._transformMap.TransformMap' object has no attribute 'get'  {code}
Answer: 1216.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: There are scatterings of {{containerd}} error messages in the jenkins build agent {{journal}}.  These do not seem to correspond with build failures.    {code:java}  Dec 06 20:53:52 jenkins-el7-1 docker[854]: time="2017-12-06T20:53:52.854292614-08:00" level=warning msg="containerd: unable to save 8f005ddebd2a06199c822adf1a136660cc5c934284aa7923a72ab137e3238e06:8fbc92cbdb763d6abe388a16e4ef9941340106ca3f52922a28e26eebf7bec109 starttime: open /proc/11597/stat: no such file or directory"  {code}    This issue suggests that this is a bug that was fixed in docker 13.x.     https://github.com/moby/moby/issues/28336    We are running docker-engine-1.12.3-1.el7.centos.x86_64 on all nodes due to storage problems that were encountered under 13.x that resulted in the version being pinned to 12.x.
Answer: 298333.0

User story: "We need a larger minimum memory footprint."
Answer: 813.0

User story: "Determine the correlation matrix empirically from blank patches of sky on a coadd, then see if we can construct a detection kernel that corrects for it."
Answer: 732877.0

User story: "Rather than use the script console, a standard job to cleanup all workspaces would be more convenient."
Answer: 426100.0

User story: "This ticket is to learn how to use the MAF and Opsim tools and data that currently exist.  The goal is to be able to take a simulation run and compute the shapes of the corresponding CCDs for each visit.  We can then start to ask questions like:  given a patch on the sky, how many CCD edges overlap the patch."
Answer: 70450.0

User story: "This ticket is to finish the paper on computing shear on coadds.    This includes:  * Running more data to increase the statistics  * Making plots for the paper  * Writing the paper."
Answer: 534392.0

User story: "Not only is the Exposure metadata much more convenient to work with, the Task metadata for coaddDriver is not even being written at present (DM-12932), so these values are lost completely most of the time."
Answer: 375.0

User story: "In the HSC detectors, charge can pool at the top/bottom of the device. The level (~ 20k) is significantly under the saturation level, so it doesn't get masked and there's no simple way to identify it. Without ignoring {{EDGE}} pixels during coaddition (removed in DM-9953), these bad pixels leak into the coadds. We need to revert commit [{{5faadffd2f408b019280ea1c353f0ec787b092b9}}|https://github.com/lsst/obs_subaru/commit/5faadffd2f408b019280ea1c353f0ec787b092b9]."
Answer: 296.0

User story: "Reprocess the HSC RC dataset, as defined in [DMTR-31 Sect. 4.1 |https://docushare.lsst.org/docushare/dsweb/Get/DMTR-31], using Stack w_2017_50.  Steps include {{makeSkyMap.py}}, {{singleFrameDriver.py}}, {{mosaic.py}}, {{coaddDriver.py}}, and {{multiBandDriver.py}} (DM-10129/DM-11020)."
Answer: 20060.0