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: "The scatter in the measurement of aerosol parameters tau, alpha is high. (see link)    [https://confluence.lsstcorp.org/display/DM/Adjustement+of+the+aerosol+component+based+on+the+airmass+dependence?preview=/73571776/73572678/Capture%20d%E2%80%99e%CC%81cran%202018-02-28%20a%CC%80%2012.04.41.png]    One possibility to reduce it could be to try a better temporal tuning of LibRadTran parameters.    So movies of weather above CTIO in October 2017 have been assembled here :    [https://confluence.lsstcorp.org/display/DM/Merra-2+Movies+October+2017]    They are under investigations,    meaning looking at the movies of all these variables :    [https://confluence.lsstcorp.org/display/DM/NASA+Merra-2+%28Modern-Era+Retrospective+analysis+for+Research+and+Applications%29+data]    1st table     "
Answer: 157080.0

User story: "To lower the barrier to getting started with interactive QA notebooks, make a script that automatically generates useful template notebooks."
Answer: 29436.0

User story: "In order to help enable others to use the interactive QA tools in {{qa_explorer}}, make sure the code is well documented.  This also means making some overview and demo notebooks that show and discuss functionality in more detail.  When this is complete, then move repo to lsst-dm, and then enlist some people as guinea pigs to try things out for themselves, prior to the DM all-hands meeting."
Answer: 134886.0

User story: "Implement a {{MultiBandCatalog}} in qa_explorer, in order to enable color-color plotting and exploration.  It should take a dictionary of coadd catalogs, keyed by filter name, and a {{QADataset}} initialized with such a catalog should calculate colors, and be able to plot color-color plots."
Answer: 29466.0

User story: "Prepare slides for presentation at the *Systems Engineering/Data Management Joint Subsystem Meeting, March 5 - 9, 2018 | Pasadena, CA* during the “Current status of QA tooling and dataset” session on Mar 7."
Answer: 3310.0

User story: "Track efforts in support of emergent QA issues in February."
Answer: 136.0

User story: "Ensure monitoring stack is fully operational on ATSCam server and have dashboard and alerts set up to monitor its health and status.  "
Answer: 50275.0

User story: "Move all Grafana instances to v5    Move all InfluxDB instances to v1.4 to support the Prometheus write API    Normal Telegraf Updates to latest version"
Answer: 1.0

User story: "Keep current with ongoing discussion, development, and documentation, and make tangible contributions as needed."
Answer: 1.0

User story: "JupyterLab is still in very active development, and often upgrades to it break our container build, make extensions refuse to install, and generally wreak havoc.  This tracks the time necessary to fix those things as they break."
Answer: 128096.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "As we think of more things to pass down to the spawned Lab container, and more knobs that need to be added to the deployment (for instance, selecting between CILogon and GitHub), then our deployment tool needs to be modified to accommodate these additional settings and generate configuration and deployment instructions for them.    Same goes for bug fixes in the deployment tool as we find corner cases where it doesn't currently work but should."
Answer: 128097.0

User story: "Run through Butler composites with [~<USER> and discuss results with [~<USER> and [~<USER>."
Answer: 32.0

User story: "Modify the usage.py and usageplot.py codes found in [https://github.com/lsst-dm/ldf_ops_tools/tree/master/usage] to allow for the creation of node usage plots that are color-coded to differentiate which codes (singleFrameDriver, mosaic, coaddDriver, etc.) use the nodes at a certain time.  This will make it more clear which codes are node-greedy and which ones are not. "
Answer: 14614.0

User story: "Do following:   * for webpack/babel to use env for pollyfills   * add webpack-visualizer-plugin: Visualize and analyze the Webpack bundle to see which modules are taking up space and which might be duplicates.   * experiment with using babel-plugin-lodash to treeshake lodash (_experiment failed, we can't use it_)   * remove fftools (we not longer us it)     "
Answer: 10345.0

User story: "Please move the processed w_2017_52 repo of DM-12982 to {{/scratch}}.  Create a link and ensure data can be assessed via the same Butler path {{/datasets/hsc/repo/rerun/RC/w_2017_52/DM-12982/}}     Please do not use the login node (lsst-dev01) for this. "
Answer: 4679.0

User story: "Warping introduces pixel noise correlations when coadding images that we do not currently track.  One way to compute the correlations would be to use the visit information to construct a noise field for each visit and then coadd them in the same way as the data.  The correlations can then be computed on the coadded noise image.  Doing this for multiple realizations can reduce the noise in such calculations."
Answer: 197130.0

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: 1589.0

User story: "Output will be a confluence page that describes what Gen3 Butler will expect from obs_* packages.  Intended audience is [~<USER> and the obs_* package working group.         Page is at https://confluence.lsstcorp.org/display/DM/Gen3+Middleware+Camera+Specialization+Interfaces"
Answer: 202827.0

User story: "This is a retroactive ticket to capture work already done: writing up    [https://confluence.lsstcorp.org/display/DM/Gen3+Butler+Composites+Design]    to guide a discussion on 2018-02-28.     "
Answer: 6.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "This is a retroactive ticket to capture work already done: writing up    [https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73570480]    to guide a discussion on 2018-02-14."
Answer: 7.0

User story: "As part of LDM-503-3, we processed 3 fields of HiTS through {{ap_pipe}} and {{ap_verify}}.  The resulting test report (DM-12534) mostly examined whether the expected products were produced.  This ticket is to do some initial scientific validation of the processed data, which is located on {{lsst-dev}} at {{/scratch/<USER>ap_verify_HiTS}}.    In particular, this may include:   * plotting histograms of the number of {{DIASources}} associated with each {{DIAObject}}   * calculating the median magnitude and RMS for each {{DIAObject}} in one band, and plotting them against each other   * plotting lightcurves for DIAObjects which are outliers on the above plots   * examining cutouts for a few DIAObjects with only a handful of associated DIASources     "
Answer: 61660.0

User story: "Currently the data stored and used in ap_association very close to the afw MinimalSourceSchema and do not contain much information beyond the object position. This ticket would add calibrated fluxes to the DIAObjects and DIASources in ap_association and create code for calculating the mean of these fluxes."
Answer: 109166.0

User story: "Define and publish interface to monitoring system for use by external applications"
Answer: 112159.0

User story: "Firm up configuration management to make sure desired software versions stay in place through system upgrades. At this point the system can go into normal maintenance mode."
Answer: 51852.0

User story: "In DM-13510 we updated LDM-503 to reflect the current milestone dates from PMCS, and instituted an auto-generation procedure to ensure that it remains up-to-date with minimal manual intervention.    Unfortunately, this means that the LDM-564 dates are now out of sync with both LDM-503 *and* PMCS: update it to be consistent, and add some auto-generation here too."
Answer: 63392.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 are a few things we need to change/confirm about the {{sqre/infrastructure/documenteer}} job:    1. We need to be able to set a list of Git Refs of packages to checkout. This is important so that developers can build/test their documentation before merging tickets. That is, I think the job needs to look like `stack-os-matrix`. (The git ref passed to ltd-mason will be based on this text, so that development builds appear as pipelines.lsst.io/v/(slug) editions.    2. We need to let a user set the git ref of the `pipelines_lsst_io` repo as well. Ideally this would come from the list of git refs in (1), but it could be a separate text entry initially.    3. The version of `documenteer` that's installed _needs_ to come from the version of documenteer listed in `pipelines_lsst_io`'s requirements.txt file. I really need this dependency to be established though the documentation repo, rather than from an external Jenkins job. Otherwise, it’ll be hard for me to upgrade Sphinx extensions and the theme while also maintaining maintenance branches of documentation."
Answer: 69385.0

User story: "Felipe attends the Telescope & Site Subsystem Meeting in Tucson.    [https://project.lsst.org/meetings/mini-jtm2018/ts]"
Answer: 73267.0

User story: "Attend DAQ tutorial/workshop and related activities in Tucson.    https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73568441"
Answer: 1.0

User story: "Jim & Htut-Khine attend the Systems Engineering and Data Management Joint Technical Meeting in Pasadena.    [https://project.lsst.org/meetings/mini-jtm2018/ts|https://project.lsst.org/meetings/mini-jtm2018/se]"
Answer: 63325.0

User story: "Jim attends the Telescope & Site Subsystem Meeting in Tucson.    [https://project.lsst.org/meetings/mini-jtm2018/ts]"
Answer: 63329.0

User story: "In DM-13632, I added a bunch of Anaconda packages into the shared stacks on lsst-dev01 in a fairly ad-hoc way. Make sure they are included in the bootstrap for the stack."
Answer: 1192844.0

User story: "singleFrameDriver/ProcessCcd of the entire HSC PDR1 dataset"
Answer: 90723.0

User story: "Based on the version/steps/configs agreed in DM-13665, process the full set of the HSC PDR1 data. Monitor the execution progress and resolve non-stack issues (e.g. issues from bad execution). This ticket contains child tasks for the reprocessing. "
Answer: 751006.0

User story: "Decide and document the stack version, task steps, and configs to be used in the S18 reprocessing of the HSC PDR1 data on the Verification Cluster (DM-13666)."
Answer: 74949.0

User story: "This will involve standard testing as well as setting up a clone VM to test future changes locally before changing the remote system."
Answer: 119751.0

User story: "Non-standard configuration; needs to be set up to test locally but transitioned for installation in Tucson before shipping."
Answer: 49199.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: "Openstack API has been upgraded, python script used to provision cluster on Galactica or NCSA are currently broken and need to use this new, nearly undocumented, API.  Other provisionning tools like kubespray will also be tested."
Answer: 64483.0

User story: "Producing spatio-temporal display of Merra-2 data is in progress,    check-out  the confluence webpage for current status    https://confluence.lsstcorp.org/display/DM/NASA+Merra-2+%28Modern-Era+Retrospective+analysis+for+Research+and+Applications%29+data"
Answer: 165903.0

User story: "Implement RFC-453. by reorganizing the topics in the Developer Guide. Redirection pages will also be implemented.    The basic structure proposed in RFC-453 (and given in attached map) is acceptable. There is some concern about the “workflow” topics, and where JIRA and GitHub fit. We’ll have to continue thinking about this as the reorganization shakes out."
Answer: 32471.0

User story: These nice before and after plots shown in DM-13410 were from a the pre-review test run. The version that got merged doesn't set SENSOR_EDGE (and consequently INEXACT_PSF) of the new EDGE pixels.     This has the effect that fewer sources measured on the coadd will have the inexactPsf_flag set. However, most (80-98%) of the EDGE pixels are also BAD or INTRP which are then  "REJECTED" which then propagates to INEXACT_PSF:    !DM-13410_vs_08_SENSOR_EDGE.png|thumbnail!    !DM-13410_vs_08_REJECTED.png|thumbnail!    !DM-13410_vs_08_INEXACT.png|thumbnail!
Answer: 6085.0

User story: "With the adoption of RFC-449, GnuTLS is a new MacOS platform prerequisite (needed to enable builds of recent releases of MariaDB). This ticket is to add it to the MacOS CI build environment."
Answer: 93337.0

User story: Ivezić et al. 2004 (2004AN....325..583I) define a "Principle Color" analysis to estimate the accuracy of the photometric zeropoint calibration.  The principle colors are defined by linear combinations of magnitudes in the SDSS bands.  The coefficients in that paper are for the SDSS filters.  To enable direct comparison with those results, derive the associated values of these coefficients for the HSC filters.  The calibration here will start with just the RC2 dataset.  A later ticket will use the full PDR1 to calibrate these coefficients.
Answer: 132657.0

User story: The current polynomial fits in the color analysis use _numpy.polyfit_, which performs a regression on the vertical offsets from the polynomial.  A regression on the orthogonal distance to the fit is preferable (and required for nearly-vertical distributions).  This ticket is to implement an Orthogonal Distance Regression using “odr” uses the _scipy.odr_ module (the _numpy.polyfit_ fit will be retained as it serves as an initial guess for the "odr" fit).         The work here will likely be done as part of the DM-13154 ticket (as plotting limits and refinements may require adjustments as a result of this work).
Answer: 125724.0

User story: "Deploy   SUIT in LSP kubernetes cluster.  "
Answer: 214674.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: "Most recent release of Tomcat is version 9. Firefly is running in Tomcat 7 and 8 currently. We need to be able to support version 9. "
Answer: 324238.0

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

User story: "Run   # visitAnalysis   # coaddAnalysis   # colorAnalysis   # compareVisitAnalysis   # compareCoaddAnalysis    with the w_2018_08 RC2 outputs from DM-13532"
Answer: 24563.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: "Read and review PUB-58: A study of the Point Spread Function in SDSS images."
Answer: 2.0

User story: "Overlapping bad amps eat up the temporalThreshold budget.     For example if a local region has 10 visits, and 3 of those visits are not included because of bad amps, then no candidates are clipped.    CLIPPED mask for {{/datasets/hsc/repo/rerun/private/<USER>RC/DM-13553+DM-134110}}: 9813, HSC-Z   !mask_DM-13553+DM-134110_9813HSC-Z.png|thumbnail!     Seen since DM-12692: Bad amps can be seen in this epochCountImage:    !Screen Shot 2018-01-25 at 12.20.55 PM.png|thumbnail!     If any detections the warpDiffs are entirely covered with the badPixelMask, then don't contribute to the rolling epochCountImage or clip. "
Answer: 80439.0

User story: "With the adoption of RFC-449, GnuTLS is a new MacOS platform prerequisite (needed to enable builds of recent releases of MariaDB)"
Answer: 97548.0

User story: "Set up a Kafka MirrorMaker service that is capable of making a copy of all or a subset of data and topics in another Kafka cluster.  This is useful for copying a Kafka service to external downstream brokers and potentially for our mini-broker if we have multiple Kafka clusters."
Answer: 47567.0

User story: "Implement RFC-452 by removing old shared stacks from lsst-dev01."
Answer: 300.0

User story: "On Slack, [~<USER> writes:    {quote}  {code}  conda install dask distributed datashader  conda install bokeh=0.12.14  conda install -c conda-forge holoviews  conda install -c ioam parambokeh  {code}  Oh, and fastparquet  {quote}    [~<USER> says:    {quote}  Is it possible to install fastparquent in the shared stack at {{/software}}? It's used in {{pipe_analysis}}.  {quote}"
Answer: 60515.0

User story: "We decided to retrieve ozone data from satellite :    Here it is              !merra2.png! A confluence page explains how to retrieve the data :    [https://confluence.lsstcorp.org/display/DM/NASA+Merra-2+%28]Modern-Era+Retrospective+analysis+for+Research+and+Applications%29+data"
Answer: 171577.0

User story: "The project has endorsed usage of C++14 for a while now.  Let's enable this in our builds so we can start making use of it."
Answer: 123.0

User story: Ran into the following errors in Python 3 stack:  {noformat}    File "/home/<USER>stack/ctrl_orca/python/lsst/ctrl/orca/ProductionRunManager.py", line 38, in <module>      from SocketServer import ThreadingMixIn  ModuleNotFoundError: No module named 'SocketServer'  {noformat}      {noformat}    File "/home/<USER>stack/ctrl_orca/python/lsst/ctrl/orca/ProductionRunManager.py", line 37, in <module>      from BaseHTTPServer import HTTPServer  ModuleNotFoundError: No module named 'BaseHTTPServer'  {noformat}      {noformat}    File "/home/<USER>stack/ctrl_orca/python/lsst/ctrl/orca/ServiceHandler.py", line 28, in <module>      from BaseHTTPServer import HTTPServer, BaseHTTPRequestHandler  ModuleNotFoundError: No module named 'BaseHTTPServer'  {noformat}
Answer: 1087.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: "Have a design discussion on Butler Registry / Datastore boundary and update the write-up of the results of said discussion."
Answer: 11450.0

User story: Do the following coverage options to the API and app config:   * Add a parameter to specify a HiPS repository or just to do a HiPS   * Add a parameter to specify the image source   * Add a parameter to specify fallover, when to move between or not to fallover    Add to the UI:   * Way to force switch to hips   * clean up any UI elements that should not be there in HiPS mode (i.e. wcs match)    User choosing images:   * When showing a hips and the user wants to add a image, what should be done? research and implement. (I might move this to a separate ticket)         fix:     when you switch coordinate systems the center of the display changes.    (step 1 and 2 of: [https://caltech-ipac.atlassian.net/browse/IRSA-1541]     related:    wcs matching:   * group locking forces hips into same coordinate system (galactic or j2000) and they scroll, zoom together   * The wcs match checkbox will not show up with only hips images or if the are less then two fits Images.   * Add a button "Match Image to HiPS" which will show when there is at least one HiPS and at least one image.  When click it will force the HiPS to scroll and zoom to same scale and outline the active FiTS image. I think this will do the most important parts of WCS match.    Related tickets:    [https://caltech-ipac.atlassian.net/browse/IRSA-1539]    [https://caltech-ipac.atlassian.net/browse/IRSA-1540]    [https://caltech-ipac.atlassian.net/browse/IRSA-1543]    [https://caltech-ipac.atlassian.net/browse/IRSA-1544]     [https://caltech-ipac.atlassian.net/browse/IRSA-1544]          
Answer: 37136.0

User story: "Do the following:        * Implement a hips sources frame work similar to the image sources frame work in server/visualize.    * It should be a search processor the merges data from more than one source   * Move the query of CDS for the firefly server - this is one hips source   * The framework should add a column to CDS for a popular flag    * Create a list of IRSA surveys from format similar to {{edu/caltech/ipac/firefly/resources/irsa-image-master-table.csv}} - this is the second hips source, the popular flag should be set on all of these.   * Framework should merge the hips sources   * On the client side there should be a filter that can modify the popular flag or add sources.   * The UI should be changes to choose the popular HiPS based on the Popular flag of the table.     "
Answer: 37544.0

User story: "The Ipac Jenkins currently send out email on build failures.  Make it send message to a IPAC slack channel.         The message could contain at least (if possible):   * URL and date of the build/console   * URL of the PR to test if build need to be tested   * Author of the last commit that trigger the build   * Last changes or git log"
Answer: 37157.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: Modify usageplot.py so that it will output stepped plots, like those shown in DM-13547 so as to better show the node usage, instead of how the current plot just "connects the dots".  Push the corrected code to [https://github.com/lsst-dm/ldf_ops_tools].
Answer: 191.0

User story: "After the Python 3 transition is fully completed, integrate the work of DM-13515 into master on GitHub. Previous codes may need to be modified to work in python 3."
Answer: 547290.0

User story: "+underlined text+When completing DM-13578, it was recognized that some of the SLURM IDs gave the following error when finding their information via sacct due to the GPSF outage on 24 Oct. 2017:  {code:java}  JobID JobName NNodes Elapsed State ExitCode  ------------ ---------- -------- ---------- ---------- --------  Conflicting JOB_STEP record for jobstep 95210.0 at line 263284 -- ignoring it  Conflicting JOB_STEP record for jobstep 95211.0 at line 263288 -- ignoring it  Conflicting JOB_TERMINATED record (COMPLETED) for job 95210 at line 263355 -- ignoring it  Conflicting JOB_TERMINATED record (COMPLETED) for job 95211 at line 263359 -- ignoring it  95210 mtWide 3 00:04:28 NODE_FAIL 127:0  95210.0 hydra_pmi+ 3 00:04:27 FAILED 7:0  95210.1 hydra_pmi+ 3 07:44:48 COMPLETED 0:0  95211 mtCosmos 4 00:04:04 NODE_FAIL 127:0  95211.0 hydra_pmi+ 4 00:04:04 FAILED 7:0  95211.1 hydra_pmi+ 4 10:10:13 COMPLETED 0:0  {code}  So while the job initially failed, it was later run successfully with the same JobID.  Modify usage.py to allow for the inclusion of such jobs."
Answer: 10798.0

User story: "Modify usageplot.py so that it will print out the total node-hours of a reprocessing campaign given a list of slurm IDs. This code should be able to work with usage.py."
Answer: 5899.0

User story: "<USER>(NAOJ) noticed that the temporary wide background (DM-13553) we remove when we detect sources on the coadds isn't being properly restored, leading to the over-subtraction of sources in large galaxies."
Answer: 344.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: {code}  fluxFitAbsolute CCD 101: 0.984778  fluxFitAbsolute CCD 102: 0.987866  fluxFitAbsolute CCD 103: 0.987659  Mosaic INFO: Write Fcr ...  Traceback (most recent call last):    File "/tigress/HSC/stack/hsc3-perseus-20171206/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/6.0b6-hsc/bin/mosaic.py", line 5, in <module>      MosaicTask.parseAndRun()    File "/tigress/HSC/stack/hsc3-perseus-20171206/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/6.0b5-hsc+2/python/lsst/pipe/base/cmdLineTask.py", line 586, in parseAndRun      resultList = taskRunner.run(parsedCmd)    File "/tigress/HSC/stack/hsc3-perseus-20171206/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/6.0b5-hsc+2/python/lsst/pipe/base/cmdLineTask.py", line 240, in run      resultList = list(mapFunc(self, targetList))    File "/tigress/HSC/stack/hsc3-perseus-20171206/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/6.0b6-hsc/python/lsst/meas/mosaic/mosaicTask.py", line 80, in __call__      result = task.run(*args)    File "/tigress/HSC/stack/hsc3-perseus-20171206/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/6.0b6-hsc/python/lsst/meas/mosaic/mosaicTask.py", line 1056, in run      numCoresForReadSource, readTimeout, verbose)    File "/tigress/HSC/stack/hsc3-perseus-20171206/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/6.0b6-hsc/python/lsst/meas/mosaic/mosaicTask.py", line 1017, in mosaic      self.writeFcr(dataRefListToOutput)    File "/tigress/HSC/stack/hsc3-perseus-20171206/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_mosaic/6.0b6-hsc/python/lsst/meas/mosaic/mosaicTask.py", line 699, in writeFcr      1.0/instFluxMag0,  ZeroDivisionError: float division by zero  {code}
Answer: 184.0

User story: "{{lsst.meas.base.tests.TestDataset}} contains two methods ({{makePerturbedWcs}} and {{realize}}) that take an optional seed for the random number generator. In both cases, the seed defaults to {{None}}, which means the RNG is seeded in some non-deterministic manner. However, this is intended for tests, which we require are deterministic. The current API therefore makes it too easy (simply neglecting to specify the optional {{randomSeed}} keyword argument) to do something bad. We should default to some deterministic value for the seed."
Answer: 280.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "Running {{coaddDriver.py}} on HSC Cosmos y-band data:  {code}  coaddDriver.py /tigress/HSC/HSC --calib /tigress/HSC/HSC/CALIB-20180117 --rerun hscPipe-6.0-beta6/20180221/cosmos --job cosmos-coadd-y --time 100 --node 1 --procs 4 --batch-type=slurm --mpiexec='-bind-to socket' --id tract=9813 filter=HSC-Y --selectId ccd=0..8^10..103 visit=22662^22660^22658^22646^22648^22644^22642^22632^22630^22628^22626^22608^22606^22604^22602^22664^62984^62992^62998^62986^62994^62990^62988^62996^62982^11736^11740^11732^11726^11730^11722^11720^11718^11742^11738^11734^11728^11724^318^320^312^316^272^274^270^322^310^314^268^266^326^308^264^242^324^306^262^302^300^258^298^296^260^256^370^294^254^366^364^368^362^360^356^292^250^288^290^248^354^286^352^284^348^350^346^342^282^244^344^280^278^246^332^334^328^276^330^358^54096^54128^54086^54098^54092^54090^54124^54100^54122^54126^54094^54088^54120^1868^1876^1862^1882^1860^1880^1878^1858^1874^1872^1870^57924^57916^57922^57914^57912^57918^57910^57920^18516^654^18478^18492^18540^640^18506^676^18480^18524^18548^18498^656^18538^634^662^18490^18544^646^18518^18482^18512^18530^18488^678^18536^650^632^18532^644^666^18502^18520^18494^664^630^652^18550^18556^18514^658^18528^18484^18542^642^18496^668^18508^636^18510^18534^18500^18552^680^18526^18546^660^674^18554^638^18522^648^18504^18486^670^89808^89814^89796^89810^89806^89794^89802^89818^89798^89812^89822^89800^89804^89820^89816^97622^97624^97610^97594^97638^97626^97612^97596^97608^97636^97598^95806^95830^95832^95804^95816^95788^95792^95802^95818^95820^95790^104166^104184^104182^104168^104170^104180^102112^102188^102162^102098^102190^102126^102160^102224^102116^102210^102178^102176^102142^102174^102100^102114^102146^102164^102194^102222^102150^102206^102220^102192^102148^102236^102196^102102^102208^102128^102130^102234^102140^105748^105738^105752^105734^105764^105762^105766^105736^105750^105778^105776^105562^105502^105588^105504^105586^105560^105532^105530^105506^105558^105534^106714^106716^106712^106710^106708^108242^108228^108234^108244^108224^108250^108222^108238^108240^108248^108230^108232^108246^108226^108236^110408^110402^110400^110392^110396^110394^110388^110398^110386^110406^110390^110410^110412^110404 -C coadd.py --batch-submit '--mem 128000'  {code}    Produces a shell script with:  {code}  #SBATCH --time=14027  {code}    to which {{sbatch}} reacts:  {code}  sbatch: error: Batch job submission failed: Requested time limit is invalid (missing or exceeds some limit)  {code}"
Answer: 904.0

User story: "After {{makeDiscreteSkyMap.py}} has done its business, it reports:  {code}  root WARN: Unable to retrieve exit status ('NoneType' object has no attribute 'exitStatus'); assuming success  {code}"
Answer: 918.0

User story: "Python 3 is buffering error messages printed to {{sys.stderr}}, which makes it difficult to identify errors when MPI aborts happen before the printed text makes it out."
Answer: 253.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> notes that:  {code:java}  the call to `curl` in `n8l::up2date_check` (in `newinstall.sh`) to be prefixed with `env LANG=C` . The message shown by curl when files differ is not always "differ" due to i18n.{code}  The easiest way to make sure that the diffs are always legible is to force {{LANG=C}} everywhere.     
Answer: 11873.0

User story: "As raised in this community post:    [https://community.lsst.org/t/data-model-for-variable-sources-at-time-of-data-releases/2695]    we currently do not have Object flux measures that are designed to yield the total flux at an epoch when combined with a difference-image flux at that epoch; this would require photometry measured on the template coadds, which in general has different input images than the deep coadds and multi-epoch fitting algorithms.  [~<USER> and I believe PSF and aperture fluxes are probably sufficient.  We should leave open the possibility that these fluxes could be measured in a way that makes them consistent with the template coadd rather than measured directly on the template coadd itself.    Computing these fluxes will not add appreciable scope to pipeline development or runtime (it's just a reconfiguration of codes we have to write and run anyway), but they should be documented in the DPDD."
Answer: 13477.0

User story: "Getting lots of chatter from numpy:  {code}  /tigress/HSC/stack/hsc3-perseus-20171206/stack/miniconda3-4.3.21-10a4fa6/Linux64/meas_algorithms/6.0b6-hsc/python/lsst/meas/algorithms/measureApCorr.py:237: RuntimeWarning: invalid value encountered in greater    fluxes > 0.0,  {code}"
Answer: 1760.0

User story: "This ticket is a link to the ongoing effort to determine aerosol content from observation of a reference star at various airmass, during photometric conditions.    The method is described here :    https://confluence.lsstcorp.org/display/DM/Adjustement+of+the+aerosol+component+based+on+the+airmass+dependence"
Answer: 174463.0

User story: "jointcal fails intermittently with a segfault in Jenkins (e.g., [here|https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/27551/pipeline/]). Valgrind reveals memory problems in {{SkyWcs}}."
Answer: 296.0

User story: "Add a YAML formatter to daf_butler."
Answer: 1255.0

User story: "Now that RFC-45 is official, update the daf_butler package to be compliant."
Answer: 43.0

User story: "To reproduce, go the By Name, enter an object name.   Then select a tab, maybe Photometry & SEDS.   Headers are displayed, but the table data is not. The user needs to click one of the icons (Filter, display format) to get the table data to appear.   CogE: Jeff"
Answer: 59079.0

User story: We get "Failed to load table. Error: Request failed: https://irsa.ipac.caltech.edu/irsaviewer/sticky/CmdSrv."   Works from Table Editor, not Filter Panel.  CogE: Jeff
Answer: 30076.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: "Example:  From By Name, click on Photometry & SEDs. Open the Table editor, click reset.  This results in a page reload, the use is not longer looking at the selected tab.   We'd like to isolate events to within the <div> passed to FireFly.  These issues no doubt arise from the way we are embedding tables into our own environment, that is into the JQuery UI tabs in pages served by our Drupal instance.   I think these problems may well be resolved by understanding and isolating events within our stack.   Note:  I had to figure out how to do the same type of behavior with Data tables to fix the sort-on-filter problem (disable event bubbling). NED can help identify the nature of the event isolation necessary to use Firefly within a complicated software stack, which contribute to the robustness of Firefly and its documentation.  CogE: Jeff"
Answer: 30075.0

User story: Filtering from the table editor appears to work.  But hitting reset from the table editor after filter results in "Failed to load table. Error: Request failed: https://irsa.ipac.caltech.edu/irsaviewer/sticky/CmdSrv”, then reloads the entire page (By Name).   The reloading of the entire page is related to ENG-632. CogE: Jeff
Answer: 30071.0

User story: Is there a way for Firefly to use two VO Table FIELDS to make a hot link?  NED's demo UI can display external references as hot links.   See b.ned.ipac.caltech.edu/byname, External References tab.   If a NED VO Table FIELD has a <LINK ... href="<FIELD_NAME"/>, a hot link will be created using <FIELD_NAME> as the href.    The service.url can be hidden, so two fields make link.  {{<FIELD ID="ext_col2" name="external_service_name" ucd="service.name" datatype="char" arraysize="*"> <DESCRIPTION>Name of related on-line astronomical service .</DESCRIPTION> <LINK content-role="query" content-type="text/xml" href="ext_col5"/> </FIELD> ... <FIELD ID="ext_col5" name="external_service_url" ucd="service.url" datatype="char" type="hidden" arraysize="*"> <DESCRIPTION> URL address of related on-line astronomical service . </DESCRIPTION> </FIELD>}} CogE: Jeff
Answer: 554064.0

User story: NED's UI displays VO Table FIELD descriptions as tooltips.   Can Firefly table display do this too?   See b.ned.ipac.caltech.edu/byname.   Select the Photometry & SEDs tab and hover over a column header.  Firefly developers have indicated that tooltips should work for this purpose, but this feature is not well documented and a JIRA ticket will request assistance.  {{<FIELD ID="main_col4" name="DEC(deg)" NEDname="DEC(deg)" ucd="pos.eq.dec;meta.main" datatype="double" unit="degrees" width="10"> <DESCRIPTION>Declination in degrees (Equatorial J2000.0)</DESCRIPTION> </FIELD>}}  CogE: Jeff
Answer: 30071.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: Syntax error in filter specifiction, e.g. "Observed Passband" > U results in internal message display to user:  Failed to load table. Error: BadSqlGrammarException:StatementCallback; bad SQL grammar [CREATE TABLE data_cdef2ea665d681650c55ca43c18264db AS (select b.*, (ROWNUM-1) as ROW_NUM from (select "No.", "Observed Passband", "Photometry Measurement", "Uncertainty", "Units", "Frequency", "NED Photometry Measurement", "NED Uncertainty", "NED Units", "Refcode", "Significance", "Published frequency", "Frequency Mode", "Coordinates Targeted", "Spatial Mode", "Qualifiers", "Comments", ROW_IDX from data where ("No." < 4) and ("Observed Passband" > U) ) as b) WITH DATA]; nested exception is java.sql.SQLSyntaxErrorException: user lacks privilege or object not found: U from:null
Answer: 30070.0

User story: "Update for February 2018"
Answer: 8901.0

User story: "Pieces of API that I have now in L1DB prototype could be useful for AP group, need to make sure that it has reasonable documentation.     "
Answer: 13904.0

User story: "I tried adding {{dagman_max_pre=2}} to the DESDM wcl file but it seems not propagated and set properly. "
Answer: 5451.0

User story: "Add monitoring for the new Kubernetes cluster."
Answer: 15925.0

User story: "Propose plan for handling DM tech notes in docushare.    There are a number of issues:    * Generating a PDF from rst tech note  * Allocating numbers in docushare.  "
Answer: 146015.0

User story: "Document the per-channel Jenkins job notifications and channels implemented in DM-13431.    - Focus on {{stack-os-matrix}}, though make documentation general to the other Jenkins jobs too.  - Document need to set  - Document how to configure the channel in Slack to not be overly noisy    See https://community.lsst.org/t/jenkins-notifications-in-per-job-slack-channel/2686?u=<USER>
Answer: 3206.0

User story: "Version two of the classifier. Building on the work done in DM-13409 a new version of a classifier. Incorporating things learnt in DM-13513."
Answer: 22834.0

User story: "A few misc corrections and typos that need to be corrected."
Answer: 38715.0

User story: "Our coaddition code currently delegates applying jointcal/meas_mosaic outputs to specialized code in meas_mosaic.  Since meas_mosaic and jointcal now produce compatible standardized outputs*, the code to apply them should move to the coaddition code.    This will mean that we start using a PhotoCalib object instead of meas_mosaic's non-standard {{fcr}} dataset (meas_mosaic currently outputs both, jointcal only the former) for the photometric correction, and it should allow us to remove any imports of meas_mosaic from pipe_tasks.    *We still need to make sure that meas_mosaic and jointcal are consistent about whether the output PhotoCalib includes the Jacobian of the WCS."
Answer: 257761.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 for FGCM to persist files via the butler, new datasets need to be added to obs_base.  Until now this has been done on my own branch.  This will be a clean update on this ticket, with comments which are now (finally) expected."
Answer: 8678.0

User story: "there's a dependency nightmare that we need to sort out. Removing antlr4 from the qserv build allows us to continue working on qserv while we get the dependency problems RFC'd and integrated into the build."
Answer: 101.0

User story: "The initial {{ap_pipe}} module had next to no tests. This ticket is to remedy that. The tests should try all the different possible ways to send input to {{ap_pipe}} and successfully run an image or two through each part of it."
Answer: 657336.0

User story: "Jointcal got caught during the RFC-45 copyright/license uncertainty and many of its files don't follow any of the proposals there. We should get them cleaned up, following whatever standard was finalized in that RFC."
Answer: 395376.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: {{scaleVariance}} fails for small images. Make coaddition algorithms more robust either by changing scaleVariance() or wrapping uses of it in a try block. I've also considered requiring a configurable number of pixels to cover a patch before its written out as a warp.   {code}  compareWarpAssembleCoadd FATAL: Failed on dataId=DataId(initialdata={'tract': 9813, 'filter': 'HSC-Y', 'patch': '8,1'}, tag=set()): IndexError: cannot do a non-empty take from an empty axes.  Traceback (most recent call last):    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/14.0-6-ge2c9487+39/python/lsst/pipe/base/cmdLineTask.py", line 408, in __call__      result = task.run(dataRef, **kwargs)    File "/software/lsstsw/stack3_20171023/stack/miniconda3-4.3.21-10a4fa6/Linux64/pipe_base/14.0-6-ge2c9487+39/python/lsst/pipe/base/timer.py", line 150, in wrapper      res = func(self, *args, **keyArgs)    File "/home/<USER>lsst_devel/LSST/DMS/pipe_tasks_DM-13410/python/lsst/pipe/tasks/assembleCoadd.py", line 363, in run      inputData.weightList, supplementaryData=supplementaryData)    File "/home/<USER>lsst_devel/LSST/DMS/pipe_tasks_DM-13410/python/lsst/pipe/tasks/assembleCoadd.py", line 1605, in assemble      spanSetMaskList = self.findArtifacts(templateCoadd, tempExpRefList, imageScalerList)    File "/home/<USER>lsst_devel/LSST/DMS/pipe_tasks_DM-13410/python/lsst/pipe/tasks/assembleCoadd.py", line 1646, in findArtifacts      warpDiffExp = self._readAndComputeWarpDiff(warpRef, imageScaler, templateCoadd)    File "/home/<USER>lsst_devel/LSST/DMS/pipe_tasks_DM-13410/python/lsst/pipe/tasks/assembleCoadd.py", line 1767, in _readAndComputeWarpDiff      log=self.log)    File "/home/<USER>lsst_devel/LSST/DMS/pipe_tasks_DM-13410/python/lsst/pipe/tasks/coaddBase.py", line 306, in scaleVariance      q1, q3 = numpy.percentile(sigNoise[good], (25, 75))    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/lib/function_base.py", line 4269, in percentile      interpolation=interpolation)    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/lib/function_base.py", line 4011, in _ureduce      r = func(a, **kwargs)    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/lib/function_base.py", line 4386, in _percentile      x1 = take(ap, indices_below, axis=axis) * weights_below    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 134, in take      return _wrapfunc(a, 'take', indices, axis=axis, out=out, mode=mode)    File "/software/lsstsw/stack3_20171023/python/miniconda3-4.3.21/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 57, in _wrapfunc      return getattr(obj, method)(*args, **kwds)  IndexError: cannot do a non-empty take from an empty axes.  {code}
Answer: 8663.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 new antlr4 package requires gcc 5.0 or greater, but Debian Jessie, on which the Qserv base containers are based, only supports gcc 4.9.  Upgrading the base containers to Centos7 + Devtoolset6 seems the best option.    This should also address currently busted Travis CI runs, and buildability of containers off latest master (sphgeom pybind11 compiler compatibility issue)."
Answer: 181629.0

User story: "These are being generated in real-time when answering questions about detection in the DRP team meeting, but I want to get everyone to review my improvements instead of just merging them (even though that's formally permitted).     "
Answer: 1209.0

User story: "With the sky correction (DM-9147, DM-13388), perhaps combined with the lower detection threshold (DM-12295), we are getting many large parent objects (> 10^6 pixels), deblending which is a burden on our compute budget. In several cases, this appears to be due to scattered light surviving the coadd process.    [~<USER> has proposed that we do a modest-scale background subtraction before detection, which should break up the large footprints; then we will restore the background before deblending so that the measurements have access to the original (good, large-scale) sky subtraction. There's a question about what scale to use in the background subtraction, which we can determine by running detection with different background subtraction scales, and seeing where we drop below the footprint size limits we've set in the deblender.    Jim also noted that after detection, we grow footprints by the size of the PSF in our standard detection routine. Instead of growing them all at once and allowing them to merge as we currently do, he suggests growing them individually, allowing the footprints to overlap but not merge. This might also help keep the large chains from forming."
Answer: 9091.0

User story: "Project the 10 exposures worth of good wavefront data I have from HSC onto their principle components.  Answer the question: how many PCs are required to explain this data?  Do this in both the CCD and telescope coordinate systems.  Which one is better?         Note - this will require some mechanism to place the different exposures onto the same footing, since they currently have wavefront data at different locations on the focal plane (corresponding to different stars in the images).  Explore both a double Zernike expansion and a k-nearest neighbors interpolation."
Answer: 31224.0

User story: "...previous fix didn't, because base docker image does not use the updated script for prereq management (prereqs are in latest/Dockerfile instead)"
Answer: 3.0

User story: "Qserv docker image builds broken after merge of DM-13458 (because libuuid prerequisite is not captured in Debian prereq install script)"
Answer: 4.0

User story: "Recently, [~<USER> has incorporated variable transmission curves into the stack.  This gets rid of the need for the temporary version in FGCM."
Answer: 42612.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> asked:  {quote}  In skyCorrection's logs, I see a lot of {{Unable to fit image for detector "1_47" into image of camera}} for the focus CCDs and ccd=9.  That didn't seem too surprising as I didn't process the focus CCDs and ccd=9.  But with a quick look at DM-13437 I'm not so sure.  (DM-13437 was merged before {{_06}})    Should I expect {{"Unable to get image for detector}} instead?  {quote}    The reason is that visualizeVisit hasn't been updated along the same lines as constructCalibs.
Answer: 1818.0

User story: "Plot the node utilization versus time of the HSC RC1 reprocessing in DM-13463.   Use [~<USER>'s existing code and improve it as needed/desired (e.g. do the plotting in python instead). Push the code to [https://github.com/lsst-dm/ldf_ops_tools]    Example plots attached.     A future application of this is to plot the node utilization of a PDR1 run given the slurm job IDs, like this [https://github.com/lsst-dm/DMTR-31/blob/master/figures/nodeUtilization.png]"
Answer: 8618.0

User story: "Current alert_stream Kafka prototype uses a single broker Kafka instance.  Build a cluster of 3 brokers and ensure that if one is inaccessible the others can receive and emit alerts.  Also, the current alert_stream Kafka cluster loses all data if a broker container goes down because the Kafka container houses all the data.  Figure out how and where to mount external volumes for Kafka and Zookeeper so that data is recovered and so that consumer offsets are recovered (consumers unaffected) if one or all brokers go down."
Answer: 43349.0

User story: "Fix a regular expression case sensitivity issue in lsst-projectmeta-kit's {{lsstprojectmeta.git.urls.parse_repo_slug_from_url}} API. Follows on DM-13512."
Answer: 1183.0

User story: "Add info to DMNT-071 about how to install a local registry. "
Answer: 44699.0

User story: "Update the docstrings and create a quick start guide for the new deblender."
Answer: 51535.0

User story: "During a pull request or an evaluation of an added feature, it's useful to have a specific version of a Firefly app up and running.      Add a job to Jenkins to build and deploy a Firefly app to a local k8s cluster.    This job should take as input; branch, env, and a label used to reference the instance running in k8s."
Answer: 14504.0

User story: "The discrepancy between aerosol determination from simulation and from observation below 400-nm is intriguing :    !plot70.png!         Ant the ratio of the two curves :    !plot71.png!         What is going on?         https://confluence.lsstcorp.org/display/DM/Aerosol+determination+from+observations+and+simulation%3A+the+blue+end+enigma     "
Answer: 132871.0