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: "TAP wants Gafaelfawr to return a 401 error with a Basic auth type so that the browser will prompt for authentication and the user can enter a token. This functionality was removed from Gafaelfawr because I didn't understand it. Add it back in and make it configurable via a URL parameter instead of a configuration option so that applications can pick."
Answer: 1400.0

User story: "[https://ci.lsst.codes/blue/organizations/jenkins/release%2Fofficial-release/detail/official-release/33/pipeline]         the job has been executed in order to get the v19.0.1.rc1.    Note that jenkins-dm-jobs has just been modified to permit official releases on a specific ENVREF.         There is no evidence in the build logs.    In one of the triggered run-rebuild we can see:    [https://ci.lsst.codes/job/release/job/run-rebuild/2053/execution/node/101/log/]    (using the classic interface, pipeline steps, there is one in red, corresponding on the unit)    that seems the lack of tests is triggering the failure:  Test reports were found but none of them are new. Did leafNodes run?"
Answer: 2634.0

User story: "Per discussion on DM-24325."
Answer: 61818.0

User story: "Take the felis YAML located here:    [https://github.com/lsst/cat/blob/u/jrbogart/desc_dc2_run12p_v4/yml/desc_dc2_run12_v4.yaml]    and put it into the tap schema database as a DDL file"
Answer: 19515.0

User story: "The nublado-hub secret is not managed by VSO in stable, and VSO isn't in the app-of-apps.  We need to update this."
Answer: 9819.0

User story: "Second sprint of learning about build process. "
Answer: 218.0

User story: "Following DMS requirements have no priority in the VCD:   * DMS-REQ-0394   * DMS-REQ-0395   * DMS-REQ-0396     "
Answer: 1113.0

User story: "Following [DM-SST meeting|https://confluence.lsstcorp.org/display/DM/2020-04-20+DM+SST+Agenda+and+Meeting+notes], try to run the metrics pipeline on the HSC RC2 medium size dataset "
Answer: 81809.0

User story: "Contribute to the evaluation of the  lsst.verify.task framework for scientific performance metrics."
Answer: 101954.0

User story: "The current OODS ingestion message only sends out the OBSID;  this is OK for Auxtel, but needs to be differentiated in ComCam.   This change will add raft name and sensor name to the OODS ingestion message."
Answer: 1373.0

User story: "lsst-web redirect corrections   This ticket had been created automatically Primavera ID: None"
Answer: 4181.0

User story: "lsst-web redirect corrections   This ticket had been created automatically Primavera ID: None"
Answer: 50174.0

User story: "Running {{processCcd.py}} is  producing \{\{afw.fits WARN: In void lsst::afw::fits::\{anonymous}::writeKeyFromProperty(lsst::afw::fits::Fits&, const lsst::daf::base::PropertySet&, const string&, const char*), key 'ext_photometryKron_KronFlux_nRadiusForFlux' may be standardized to uppercase 'EXT_PHOTOMETRYKRON_KRONFLUX_NRADIUSFORFLUX' on write.}} errors.    Fix this."
Answer: 33259.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: We recently started to see some registry files turn up in obs_lsst after running the tests:  {code}  data/input/phosim/calibRegistry.sqlite3  data/input/ts3/calibRegistry.sqlite3  data/input/ucd/calibRegistry.sqlite3  {code}  Making the {{data}} directory read only tells me that it's the 2to3 tests that are causing the problem.    {code}  self = <lsst.obs.base.gen2to3.calibRepoConverter.CalibRepoConverter object at 0x7f96729fea90>        def insertDimensionData(self):          # Docstring inherited from RepoConverter.          # This has only been tested on HSC, and it's not clear how general it          # is.  The catch is that it needs to generate calibration_label strings          # consistent with those produced by the Translator system.  >       db = sqlite3.connect(os.path.join(self.root, "calibRegistry.sqlite3"))  E       sqlite3.OperationalError: unable to open database file  {code}    I'm not sure if this is a bug in running the converter or if the routine should return without error if the sqlite3 file is not present (I guess sqlite3 creates the file if it does not exist).      
Answer: 26032.0

User story: "* Standardize repo layout   * Update CSC to be ConfigurableCSC   * Update CSC to use latest salobj features"
Answer: 244982.0

User story: "This follows the pattern used for other Registry systems.  After this change, we could consider giving Datastore instances these classes and a manager for the opaque tables instead of a full Registry, would be better for interface segregation.    The default implementation of these manager/storage classes should not modify the current schema, but it will give us flexibility to change it via configuration in the future, so it probably still merits being part of the stability milestone."
Answer: 23044.0

User story: "Adding the right indexes - once we determine what they are - should be easy after DM-21764.  Stay tuned for a follow-up post on that here."
Answer: 2957.0

User story: "Neither our docs nor the NCSA VPN docs say specifically which profile to use when logging in to the VPN for use with the Science Platform.  I'll add a note that {{ncsa-vpn-default}} is the one to use unless you know better."
Answer: 417.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 scarlet developers are looking at moving to JAX for performance reasons, and to future proof the code. This ticket is to create the autograd to JAX port and quantify the performance improvement."
Answer: 14695.0

User story: "Part of https://jira.lsstcorp.org/browse/CAP-164"
Answer: 16041.0

User story: "This task is to create docker container for Operation Manager"
Answer: 15904.0

User story: "The NCSA Test Stand needs to be updated SAL 4.1.0 and ts_xml 5.0.0"
Answer: 11.0

User story: "In {{kafka-aggregator}}, Faust agents aggregate the data stream on tumbling windows of fixed size (see DM-24403). Faust Records describe the data structure for the aggregated topics and with {{faust-avro}} we can serialize that to Avro.    Generally, a field representing a value in the source topic will have the corresponding aggregation fields e.g. min, mean, median, and max in the destination topic.     In DM-24485 we demonstrated that we can parse a Faust Record into an Avro schema with {{faust-avro}} which allows us to register schemas for the aggregated topics in the Schema Registry.    However, we still need to create the Faust Record for the aggregated topic in the first place.    The goal for this ticket is to demonstrate we can create the Faust Record classes dynamically, otherwise, we would have to pre-generate a large amount of static code to create Faust Records for each schema we have in the EFD."
Answer: 56283.0

User story: "Replace authnz with Gafaelfawr on int."
Answer: 7358.0

User story: "Replace authnz with Gafaelfawr on the NCSA test stand cluster."
Answer: 7364.0

User story: "Replace GitHub auth with Gafaelfawr on the base cluster."
Answer: 24556.0

User story: "Replace authnz with Gafaelfawr on int."
Answer: 4548.0

User story: "Write an implementation of CollectionManager and its associated Record classes that uses a totally hidden autoincrement integer primary key instead of just using the name as the key.    The existing NamedKeyCollectionManager (https://github.com/lsst/daf_butler/blob/master/python/lsst/daf/butler/registry/collections/nameKey.py) will probably be useful as a reference.    I'm guessing we'll find some parts of NamedKeyCollectionManager that we might want to factor out for sharing, and a few spots elsewhere in Registry that are not careful to use CollectionManager.getCollectionForeignKeyName instead of assuming a literal, though I think there's a chance I'll also clean up any of those that exist on DM-21764."
Answer: 17515.0

User story: "Fill out general_csv_overview with more detailed information."
Answer: 14841.0

User story: "Get astrometry working for the AuxTel now that we're on sky."
Answer: 167454.0

User story: "This task will put the haxapod code by MOOG to a new repo and reorganize the code structure. The autotool related code will be rewritten to fit the new structure as well."
Answer: 24730.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 task will use the factory pattern for the deblending algorithm to let UW team experiment multiple deblending algorithm without the affection of code body."
Answer: 17245.0

User story: "This task will add the cwfs parameter files of auxiliary telescope in ts_wep and do the related test based on [AuxTel2001.ipynb|https://github.com/<USER>cwfs/blob/master/examples/AuxTel2001.ipynb]. The upstream [cwfs|https://github.com/<USER>cwfs] code also fixed some bugs when evaluating the auxiliary telescope data. This task will need to put those fix into ts_wep as well."
Answer: 19036.0

User story: "Load a small set of chunk inside CC-IN2P3 Qserv cluster using replication system.    The procedure is based on: [https://confluence.lsstcorp.org/display/DM/Live+demo%3A+test+ingest+of+a+subset+of+one+track+of+the+HSC+Object+catalog]"
Answer: 168349.0

User story: "As noted by myself and [~<USER> (see slack discussion here: [https://lsstc.slack.com/archives/C978LTJGN/p1586790799028900),] running {{visualizeVisit.py}} (directly or via {{skyCorrection.py}}, rather than producing a a single full focal plane (subsampled) image, it outputs a (subsampled) image for each ccd.  At the least, the templates in the {{lsstCamMapper.yaml}} policy file need updating (but there may also be issues with the levels [not] defined in that file)."
Answer: 58973.0

User story: "There is a script in {{ci_hsc_gen3}} that does the desired steps but doesn't allow for the customization the generic script would need: [https://github.com/lsst/ci_hsc_gen3/blob/master/bin.src/ingestRaws.py]    the ingest task is here: [https://github.com/lsst/obs_base/blob/master/python/lsst/obs/base/ingest.py#L160]    For the command-line script, we'll want to create (and apply overrides to) a {{RawIngestConfig}} instance, use that to construct a {{RawIngestTask}} instance, and then call {{RawIngestTask.run}}.  This will be a common pattern for a lot of commands, and we have a history of {{-c <override>}} and {{-C <config-file>}} options (in {{CmdLineTask}} and {{pipetask}}) to apply the config overrides in a consistent way; [~<USER> can find the code in {{pipe_base}} or {{ctrl_mpexec}} that we could build on.  "
Answer: 36398.0

User story: "We'd like for the homepage of [www.lsst.io,|http://www.lsst.io,/] the Rubin search site, to have a prominent search box where the user can enter a query. The search will take the user to the Advanced search page where results are shown and the user can make further refinements.    This functionality implies that the Advanced Search page's search state should be reflected in its URL. That way the homepage search can link to the advanced search page with the search terms in its parameters."
Answer: 6936.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 [www.lsst.io's|http://www.lsst.io's/] advanced search page, we'd like a HierarchicalMenu component to allow us to refine the the search based on content type. In DM-24241 we added a {{contentCategories.lvl0}} and \{\{lvl1}} key that classifies documents in the hierarchy.    Level "0" is "Documents" and levels 1 are document series (e.g. LDM, DMTN).
Answer: 6993.0

User story: "In order to do patch release 19.0.1, it is required to use an older scipipe_conda_env reference.    Therefore the possibility to specify which ENVREF to use shall be added to the Jenkins release/official-release job"
Answer: 61742.0

User story: Update the assignment of LSST_DDS_DOMAIN for the Archivers to be "base" and "ncsa", depending on where they'll be running.
Answer: 5790.0

User story: "New cluster at base: kueyen.   ArgoCD (but not LSP) it."
Answer: 1704.0

User story: "Update ts_FiberSpectrograph code that writes images to S3 for changes in ts_salobj v5.9.0. This should be a trivial change.    Add a revision history."
Answer: 1521.0

User story: "It's clear we're missing a lot of standard, useful columns (many of them already enumerated in the ObservationInfo class) in the exposure, visit, and detector tables.  We should try harder to get this list complete before we declare the Registry schema stable to reduce the number of migrations we have to do afterwards.    This includes:    * Target name (for ObsCore)  * RA/Dec/rotation angle/rotation coord  (so that we can calculate visits without reading the raw data file)    Also includes changes to obs_base to use the ra/dec in visit region calculation."
Answer: 167195.0

User story: "Make sure that the DCS can accept all commands and that the mock controller returns sensible replies."
Answer: 25901.0

User story: "Make sure that the DCS can send configuration parameters to the lower level components."
Answer: 5919.0

User story: "Garry Knight has prepared a raspberry pi disk image which needs to be installed."
Answer: 4.0

User story: "Some changes were necessary during observing, I think all just config changes, but these hastily shoved onto a user branch so that observing could continue.    This ticket is to incorporate them properly."
Answer: 1775.0

User story: "T&S are doing a pass through all the CSCs, updating information about what constitutes a ConfigurableCSC.    After talking with [~<USER>, I'm going to convert the CCArchiver to a BaseCSC.  (There's also going to be a change for ATArchiver).    I'll also update that necessary information in ts_xml as part of this ticket."
Answer: 188021.0

User story: "T&S are doing a pass through all the CSCs, updating information about what constitutes a ConfigurableCSC.    After talking with [~<USER>, I'm going to convert the ATArchiver to a BaseCSC.  (There's also going to be a change for CCArchiver).    I'll also update that necessary information in ts_xml as part of this ticket."
Answer: 188019.0

User story: "GH auth broke under new logging"
Answer: 1075.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: Per RFC-687, remove the deprecated status from certain methods associated with {{Background}}, {{BackgroundList}}, and {{BackgroundControl}}. Specifically:    * revert [lsst/afw@7038c57|https://github.com/lsst/afw/commit/7038c57dc1f0ddd14cba6701bb65da10cdaea557], [488744f|https://github.com/lsst/afw/commit/488744f7d9a89d799963403493304a4b7e211849], and [29ec3d3|https://github.com/lsst/afw/commit/29ec3d3465866cdd0785a75ba73eeb6a4f4a717d], removing the use of deprecation attributes/decorators for the code in question  * after reverting these changes, update the documentation to not describe the affected components as deprecated    This will leave the code with both "old" and "new" APIs for doing certain things; because of the past deprecation period, Stack code will be slightly biased towards the "new" APIs. Addressing this balance is out of scope for this ticket.
Answer: 12473.0

User story: "Now that we have two tasks we can make a pipeline that is not completely trivial.  Write runnable pipeline description that links catalog construction with metric measurement."
Answer: 2623.0

User story: """recommended"" tag resolution is failing again."
Answer: 1230.0

User story: "Support build and deployment of TSS components at NCSA. "
Answer: 21272.0

User story: Add LSST_DDS_DOMAIN, make it configurable, "nosite" if a non-SAL site.
Answer: 1300.0

User story: change repo from a required "option" to a required "argument" (former has flags e.g. {{--repo foo}}, the latter is positional).
Answer: 17369.0

User story: {code:python}instr = getInstrument(instrument)  {code}  should be   {code:python}instr = getInstrument(instrument, butler.registry)  {code}  like in register_instrument    Make that change, and add a test to obs_base like the ingest_tests.py that obs packages can run to ensure that these commands work. At the moment it can run create -> register-instrument -> write-curated-calibrations and ensure they work (with write-curated-calirations using the name not the class).    Also add a test_cli.py file to each obs package specfiying the instrument class, e.g. make obs_decam/subaru/lsst have a trivial test file that inherits from it and specifies the instrument class to use.         Found during development of the test, the docstrings in obs_base utils.py getInstrument.py and instrument_option are wrong and should indicate "canonical name of the instrument or the fully qualified Instrument class name".
Answer: 11641.0

User story: "Record a measurement in SQuaSH of how quickly salobj can read and write writing DDS samples. Ideally we would record separate values for writing and reading. Note that the existing speed test testss/test_speed.py only measures the combined speed of reading and writing.    See https://github.com/lsst-sqre/notebook-demo/blob/master/lsst-verify-squash/LSSTVerificationSQuaSHDemo.ipynb for instructions."
Answer: 23232.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: "Currently the task just matches any source that is close to the output patch.  We need to trim to the patch so we aren't lying to downstream tasks."
Answer: 176.0

User story: "There have recently been discussions regarding {{Defects}} where new defects are appended to the existing list of defects. This works fine but can result in a situation where lots of tiny bounding boxes could be represented by a few large bounding boxes. Many things become more efficient if the minimal set of bounding boxes is used by downstream processing.    This ticket will add a normalize method to {{Defects}} that will recalculate the defect bounding boxes. One implementation could be to generate a mask from the defects and then recalculate the defects from the mask. This would have the side effect of allowing direct comparison of two different Defects instances."
Answer: 30270.0

User story: "There are some components that were left out of the {{FitsExposureFormatter}}.  These are defined [here|https://github.com/lsst/daf_butler/blob/master/python/lsst/daf/butler/formatters/fitsExposureFormatter.py#L100].  Basically any function defined on the {{ExposreFitsReader}} can be defined there.  See the [header|https://github.com/lsst/afw/blob/f570990def94c74c425d919df9f56a40e06715f2/include/lsst/afw/image/ExposureFitsReader.h#L120] for the method to read the {{photoCalib}} object for example."
Answer: 1554.0

User story: "Make a driver script (similar to singleFrameDriver) that can be used to easily add fakes at a larger scale during RC runs. A bonus would be to also make the `source` tables that amalgamate all the ccds."
Answer: 21371.0

User story: "Provide Science Pipelines 19.0.1 patch release including the fix of DM-24523"
Answer: 63522.0

User story: "Based on my timing tests astropy.time is 300 to 400 times slower than my custom code when converting scalar unix UTC time to TAI. Profile the code and see if there is some way to improve this to the point that I could astropy's code for lsst.ts.salobj.tai_from_utc, instead of my custom code."
Answer: 9.0

User story: in this:    [https://github.com/lsst/obs_base/blob/master/python/lsst/obs/base/cli/cmd/register_instrument.py#L33]    the command name in   {code:java}  @click.command("register_instrument")  ...  def register_instrument(...)      ... {code}  is wrong, "register-instrument" is wanted. But also it's unnecessary because Click automatically uses the function name as the command name, and also changes the underscore to dash to be unix-like in CLI commands. So just remove the places where the command name was defined and not needed.     
Answer: 10053.0

User story: "currently subcommand plugin registration is last-one-wins, which is no good. We want to identify conflicting subcommands, and fail with a message like “Command <cmd> exists in packages <one> and <two>. Duplicate commands are not supported, aborting.”"
Answer: 10058.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: "So there's been interest in logging recently, so logging a few story points against it:    1) Adam noticed that the logs were taking up more disk than usual.  I've traced this down to runaway logs from the kafka parts of the EFD.  This made the indexes from 1.5 gb / day on average to 15 gb / day (10x).  This means that it filled up the disk even before the retention rate.    2) I'm going to work on deploying the new version anyway, which has better measures for log retention.  This will also allow me to get roundtable and lsp back in sync."
Answer: 236562.0

User story: "Create skeleton pages for General Overview of CSCs per [~<USER>'s request."
Answer: 4201.0

User story: "DM-24062 added the pipelines of generating the source tables in parquet.   Add the pipelines to {{ci_hsc_gen2}}.  "
Answer: 24791.0

User story: findDefects.py seems to be taking an unusually long time to finish, e.g., I had to kill the task after a few hours for a list of visits that, in the past, did not take that long (problem originally found when trying to address DM-23762):     Command (w_2020_16):   {noformat}  findDefects.py /project/shared/auxTel-20200207 --rerun <USER>2020FEB17_auxtel_use_defects_false_2020APR21 --visitList 2020012700243..2020012700247^2020012700389..2020012700420 --id detector=0 -c writeAs=BOTH   {noformat}    Log: "output_findDefects_w_2020_16.txt"    The above command is the same (except for the name of the rerun directory) that was run in DM-21720 to produce auxTel defects (w_2020_07), and that was not taking hours to finish. I have confirmed that if w_2020_07 is loaded again, then the same command does finish in a time of the order of minutes:     Log: "output_findDefects_w_2020_07.txt"  
Answer: 18741.0

User story: "The NCSA Test Stand needs to be updated SAL 4.1.0 and ts_xml 5.0.0"
Answer: 250.0

User story: "Review and update LTS-646 (there is at least misleading reference to Modbus-ida.org)."
Answer: 116516.0

User story: "So far DCS has assumed that there will be one entry point for communication with the LLCs. However, it needs two entry points: one for the fixed part and one for the rotating part. Make sure that this gets implemented."
Answer: 4336.0

User story: "Create a mock cloud sensor that publishes cloud sensor data every 3 seconds."
Answer: 261.0

User story: "In DM-23671 we refactored datastore deletion into a two pass trash and empty. This allows us to simplify the logic in prune."
Answer: 9288.0

User story: "Forwarder supports only live streaming mode, which isn't feasible for use with CatchupArchiver. This will add support for both live and catchup streaming images."
Answer: 50297.0

User story: "Two methods, report_summary_state and call_fault, should be moved to the dm_csc base class so they can be used by additional CSCs that aren't specifically archiver CSCs."
Answer: 1208.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 lsst log tool needs to be initialized by the Click command line interface scripts, similar to     [https://github.com/lsst/pipe_base/blob/master/python/lsst/pipe/base/argumentParser.py#L497-L508]          "
Answer: 135301.0

User story: In ts_CBP/lsst/ts/cbp/statemachine.py there a syntax error at line 262 (a missing {{_}} in the f-string):  {code}  raise salobj.ExpectedError(f"{simulation mode} is not a valid value")  {code}    Please fix it
Answer: 8560.0

User story: "There is a trailing {{.}} in ts_ATWhiteLightSource/python/lsst/ts/ATWhiteLightSource/wlsCSC.py at line 79:  {code}          self.telemetryLoopTask = done_task.  {code}    Please remove it!"
Answer: 57757.0

User story: "I have not run MultiProFit on COSMOS/HSC UDeep data since DM-23399 added background level fitting. Also, the previous runs were using an older rerun with PDR2-style background subtraction (DM-21386). This ticket will run with and without background fitting on the older rerun as well as the latest PDR3?-style rerun (DM-24359)."
Answer: 70871.0

User story: "This task covers the time spend creating agendas, coordinating meetings and ultimately facilitating the next TMA software change request proposal. "
Answer: 14809.0

User story: "Start the documentation of the CSC deployment system by describing the Helm chart and ArgoCD setups. The doc will live here: https://tstn-019.lsst.io/"
Answer: 38626.0

User story: "vault tokens need rekeying for int again"
Answer: 1.0

User story: "On https://jira.lsstcorp.org/browse/DM-24324 we are beginning to incorporate the {{lsst.alert.packet}} code into the production pipelines.  We need to make it readily available to systems like Jenkins.    This ticket is to     * move the sample_avro_alert repository to the lsst Github organization  * rename the repo alert_packet for consistency  * add it to lsst_distrib"
Answer: 58870.0

User story: "Create a draft outlining description of CSCs consisting of the Auxiliary Telescope.   * Overview   * Description   * List of CSCs"
Answer: 11710.0

User story: "As per https://community.lsst.org/t/pex-config-configs-now-know-where-they-are/4023,  use {{os.path.dirname(\_\_file\_\_)}} instead of {{getPackageDir}} in obs-package config files.    I'm doing just obs_lsst, obs_decam, and obs_subaru on this ticket because I already did the work before deciding it didn't belong as a side-commit on the ticket I was working on.  Others are welcome to take care of other packages on other tickets.    "
Answer: 2328.0

User story: "This ticket is to make changes based on PO meeting comments on 2020-04-15. Nominally focused on clarifying the expectation about code in notebooks, plus several minor changes suggested by andy C."
Answer: 6874.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 ATAOS has a set of commands that enable users to set offsets on the LUTs. These commands returns before the offset where actually applied to the components which creates some operational issues. This ticket is to make sure the commands only returns once the offsets where taken or the command is rejected if the offset is not allowed.     We will also implement a command that allow users to specify a value for a axis. The ATAOS will then compute the appropriate offset that needs to be applied on the LUT. "
Answer: 213177.0

User story: "ts_sal has a few test for communication between salobj and SALPY. At least one of these has become much less reliable.    The possibilities I have thought of are:  * The memory leak fix to OpenSplice. I can test this by running an older Docker image.  * Changes in ts_sal 4.1.  * Whatever is causing the new segfaults that I reported in DM-24461, which is most likely one of the items above.  * Change in salobj. This seems unlikely, because none of the changes seems even remotely relevant.    I have no idea how long this will take to resolve, so I have arbitrarily assigned 2 story points. Given the possible association with DM-24461 I am making this a priority and adding it to the current sprint. I hope to resolve it before releasing salobj v5.9"
Answer: 1254.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 at least two packages of interest in PyPI to enable Avro in Faust applications.    I first looked at the [python-schema-registry-client|https://github.com/marcosschroh/python-schema-registry-client] package which implements a synchronous Confluent Schema Registry client and a [codec for Faust|https://github.com/marcosschroh/python-schema-registry-client/blob/master/schema_registry/serializers/faust_serializer.py].    See more about Faust codecs and using different serializers in the [Faust documentation|https://faust.readthedocs.io/en/latest/userguide/models.html#codecs].    The other package out there is [faust-avro|https://github.com/masterysystems/faust-avro] which also implements an Avro codec and Confluent Schema Registry support for Faust.    Looking at the code {{faust-avro}} seems more attractive for its hability to [parse a Faust record into an Avro schema |https://github.com/masterysystems/faust-avro/blob/master/faust_avro/parsers/faust.py] I think that's an important feature missing in the {{python-schema-registry-client}} which assumes the Avro schema is provided in addition to the Faust record (see [here|https://github.com/marcosschroh/python-schema-registry-client/blob/master/schema_registry/serializers/faust_serializer.py#L32]).    In addition, the {{faust-avro}} implementation is asyncio based. A drawback, however, is that it subclasses the Faust base classes like {{faust.app.App}}, {{faust.serializers.codec.Codec}}, {{faust.serializers.schemas.Schemas}}, {{faust.models.record.Record}}, {{faust.types.topic.Topic}}, etc but that also makes using it much easier as we show in this ticket.    Perhaps a hybrid solution would be to use only the parsers implemented in {{faust-avro}} and our own library {{kafkit}} that already implements an async schema registry client.    I think that implies rewriting [faust_avro/serializers.py|https://github.com/masterysystems/faust-avro/blob/master/faust_avro/serializers.py] using kafkit as a [codec for Faust|https://github.com/marcosschroh/python-schema-registry-client/blob/master/schema_registry/serializers/faust_serializer.py] similar to what [python-schema-registry-client|https://github.com/marcosschroh/python-schema-registry-client/blob/master/schema_registry/serializers/faust_serializer.py] does.  However, I don't know if that's possible without changing the {{faust-avro}} source code."
Answer: 10580.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: nublado currently must have the signing key for JWTs explicitly configured, which makes configuration harder. Instead, have it automatically retrieve the key from the well-known endpoint of a configured issuer URL.      {noformat}  import json  import sys    from cryptography.hazmat.backends import default_backend  from cryptography.hazmat.primitives.asymmetric.rsa import RSAPublicNumbers  from cryptography.hazmat.primitives.serialization import Encoding, PublicFormat    from jwt_authorizer.util import base64_to_number      with open(sys.argv[1]) as f:      jwks = json.load(f)  n = base64_to_number(jwks["keys"][0]["n"])  e = base64_to_number(jwks["keys"][0]["e"])  numbers = RSAPublicNumbers(e, n)  public_key = numbers.public_key(default_backend())  pem = public_key.public_bytes(      encoding=Encoding.PEM,      format=PublicFormat.SubjectPublicKeyInfo  )  print(pem.decode())  {noformat}  
Answer: 103524.0

User story: "Prepare the MTAOS docker image that adapt the ts_xml v5.0."
Answer: 10020.0

User story: "In order to use the Gen3 {{MetricTask}} pipeline task, we need to make tasks that can produce the data products used by the metric measurements.    This is to produce the product most commonly used by currently implemented {{validate_drp}} measurements, the per band matched catalog.    Results will be check into [this repository|https://github.com/lsst-dmsst/metric-pipeline-tasks]."
Answer: 1377.0

User story: When I added Datastore.export a while back, I totally punted on implementing anything other than in-place "exports" that just produce the YAML description of what's been exported.    We definitely want to implement at least copy, and probably some linking in PosixDatastore, too.    [~<USER>, I imagine you'll want to implement copy export for S3 at some point, too.
Answer: 152976.0

User story: "Open ports for use of Dask on HTCondor cluster hosts:   - sub (schedd/workflow) nodes will be the scheduler hosts   - compute (execd) nodes will be the worker hosts"
Answer: 1094.0

User story: "While checking out the new Gaia DR2 refcats in testdata_jointcal with jointcal, the astrometry tests were failing to converge. After some exploration, I discovered that the coordinate error fields were incorrect: the ingest code was assuming they were radian, when they were actually milliarcsecond.    I've already written most of the code to test this as part of verifying that it exists. Once I'm satisfied, I will re-run the Gaia DR2 ingest, and then replace the testdata_jointcal refcats (which is now trivial, with the new scripts from DM-24392)."
Answer: 9014.0

User story: "Review the Dome Software Timeline and bring it in line with the current status and the expected the development progress."
Answer: 1865.0

User story: "Introduce a polling mechanism for the lower level statuses and emit telemetry."
Answer: 1958.0

User story: "Review the M2 wish list by Bo:  [https://docs.google.com/document/d/1z_UoaHy32q6yP8ebxfQwK8SL3ThtH0KS8Se--eNcX5A/edit]"
Answer: 15286.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: "Originally discovered by [~<USER>     How to reproduce:  {code}  source /software/lsstsw/stack/loadLSST.bash  setup lsst_distrib -t w_2020_15  processCcd.py /datasets/hsc/repo/ --rerun private/<your_rerun>  --calib /datasets/hsc/repo/CALIB  --id visit=1252 ccd=3^4^5  {code}    log attached.  DM-23044 is the primary suspect. [~<USER>, will you take a look?    {quote}<USER>cactus:  7:19 PM  Does this not trigger in CI because we don’t linearize in the CI dataset?    <USER> 7:36 PM  scons in ci_hsc_gen2 launches a separate process for each ccd, which is why this didn’t trigger…. e.g.  root INFO: Running: /software/lsstsw/stack_20191101/stack/miniconda3-4.5.12-4d7b902/Linux64/pipe_tasks/19.0.0-10-g448f008b+2/bin/processCcd.py /project/<USER>ci_hsc_gen2_default/DATA --rerun ci_hsc --id visit=903344 ccd=11 --doraise -c charImage.doWriteExposure=True    <USER> 7:44 PM  I’ll file a ticket. If you’re seeing this message because you slack-searched “RuntimeError: Detector names don’t match” and want to run processCcd on more than one ccd:  either roll back to w_2020_14 or add --config isr.doLinearize=False{quote}      "
Answer: 5633.0

User story: "In comparison with MOPS, Heliolinc2 finds about half of the objects that MOPS finds. Improve this!"
Answer: 20160.0

User story: Tony says to change {color:#1d1c1d}"prime CCS author" -> "CCS manager".{color}
Answer: 4.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: "Fill out the technical portion of a CR document, requesting all of the changes that have already been made to the API between T2SA and ASC since the last version of the interface document was formally recorded in the system"
Answer: 20079.0

User story: "SAL 4.2 will allow topics to have no user-added fields. Update the XML for my CSCs accordingly, especially Test, because that will exercise this capability.    This will have to wait until we have switched our test stands and site to SAL 4.2    Consider ditching the Alias tags at the same time."
Answer: 110356.0

User story: "Continue update of software interface documentation, to make consistent with the new partition of development of control software by Rubin Observatory and EIE contractor, as we continue to settle on details."
Answer: 19861.0

User story: "Prepare and coordinate weekly meetings on dome control software with EIE contractor."
Answer: 19862.0

User story: "Ensure necessary packages installed. Configure ssh client config.  This ticket had been created automatically Primavera ID: None"
Answer: 2570.0

User story: "This ticket is to be completed by Sam Cappon, the intern.    Forwarder's name comes from static variable in the config file, which is not scalable across different versions of forwarders in different machines. This ticket improves upon already existing code to get hostname:ip address as the name of forwarder."
Answer: 37334.0

User story: "The wavefront sensors need to be defined as a separate kind of raft since the corner rafts contain multiple kinds of sensors, and currently yaml camera assumes all rafts are homogenous in their detector types.  To do this the yaml files append a 'W' to mark wavefront sensor rafts, but since the in memory camera doesn't care about this distinction, we can strip it out when building the full camera yaml.    [This|https://github.com/lsst/obs_lsst/blob/master/python/lsst/obs/lsst/script/generateCamera.py#L236] is where the stripping happens.  Instead of assuming a delimiter, I think I'd like to go to an explicit name translation mapping: e.g. {{output_name = nameTranslator.get(input_name, input_name)}}."
Answer: 4046.0

User story: "- Update the milestones repository with data extracted from PMCS ()   - Update LDM-503, LDM-564, images repository ()   - Update milestone dates loaded into Jira ()   - Update skeleton March 2020 monthly report (x)   - Audit and update [https://confluence.lsstcorp.org/display/DM/DM+PMCS+Update+Requests] ()"
Answer: 125272.0

User story: "Build a model that connects to the ADAM and can read voltages off the analog inputs."
Answer: 34516.0

User story: "Most of the work is done to get the versioning for Java correct.  But now those files need to be pushed to Nexus.  The jobs will need to be update accordingly.  This task covers that work."
Answer: 14408.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: "While the current Kafka producer Helm chart gets the job done, it does not really allow for flexible specification of the number and grouping of CSCs. The next iteration should make that possible."
Answer: 22007.0

User story: "1) Meeting with Matthew and Eric to discuss documentation.    2) Producing a documentation proposal and collaborating with high level tree being produced by management."
Answer: 5731.0

User story: "Currently scarlet uses autograd to calculated the gradients used for optimization. This creates an overhead in both memory and runtime, as autograd requires a wrapper for all functions used in the code in order to back-propagate the gradients for each variable.    For scarlet we can calculate almost all of those gradients ourselves, eliminating the need to use autograd. The attached notebook demonstrates how this can be done, giving an outline of the runtime differences between autograd and direct gradients using a simplified modeling algorithm with a single back-propagation. It also demonstrates that gradients can be back-propagated up to 10 times faster per iteration when using gradients that we calculate ourselves, where the exact saving is based on the ratio of the PSF to the full size image (which translates into how much time we are spending on gradient calculation vs convolutions).    DM-23788 implements convolutions in real space, resulting in a model that allows us to calculate all of the gradients directly ourselves. However, it also demonstrates that real space convolutions are slower than those performed in k-space, so we are likely to use fft convolutions in production. We could in principle still use autograd to calculate the FFT convolution gradients for us, however since we only need the gradients for that single operation it will likely be easier to just implement a direct gradient for the FFTs as well (which may be as simple as calling a function in autograd)."
Answer: 43146.0

User story: "Review LTS-89 document."
Answer: 197.0

User story: "For testing pipelines and algorithmic changes in AP it would be useful to be able to run ap_verify against ticket branches in Jenkins, similar to ci_hsc.  This ticket is to modify the Jenkins pipeline to make it possible.    The current ap_verify CI pipeline runs nightly and auto-uploads the resulting metrics to SQuaSH; we have to determine what behavior is desired for runs on ticket branches."
Answer: 77618.0

User story: "This work is gonna be completed by Sam Cappon, current intern.     Currently, we are using wide-open redis instance. Anyone can have access to the database. So, authentication mechanism, password protection, is a good to have. This ticket addresses the efforts to add password to current C++ RedisConnection class."
Answer: 238812.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: I received an error when rebuilding the stack, related to the new "smart" symlink mode:    {code}  E       FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpxhaie4yi/raw/DECam/raw/g/g DECam SDSS c0001 4720.0 1520.0/411371/raw_g_g DECam SDSS c0001 4720_0 1520_0_411371_411371_56_DECam_raw_DECam.fits'  ../../lsstsw/stack/Linux64/daf_butler/19.0.0-50-g09080728+1/python/lsst/daf/butler/datastores/posixDatastore.py:400: FileNotFoundError  {code}    This was apparently due to attempting to hard link a symlink in the `transfer=='link'` mode in posixDatastore. [~<USER> suggested a fix by using `os.path.realpath(fullPath)` at all calls to `link`.
Answer: 231.0

User story: "As per [the prototype|https://confluence.lsstcorp.org/display/DM/Architectural+Prototype+for+the+New+Gen3+Registry], add CALIBRATION-type collections that include a validity range in associations, and remove the calibration_label dimension.  Update downstream code."
Answer: 243359.0

User story: "Between 26 & 27 March, the {{fracDiaSourcesToSciSources}} (“Ratio of DIASources to Direct Image Sources per CCD”) being tracked by Chronograf very ap_verify_ci_hits2015 changed for unknown reasons. What happened?"
Answer: 1016.0

User story: "When DM-17597 is complete, a new PS1 reference catalog will be available in {{testdata_jointcal}}.  The {{fgcmcal}} tests will be updated to make use of the improved reference catalog (and updated catalog format)."
Answer: 75876.0

User story: "[~<USER> has is changing the main telescope camera rotator low level controller to transition from FAULT to STANDBY when it receives the clearError command, instead of to OFFLINE/PUBLISH_ONLY.    I hope and assume he plans to do the same for the low-level hexapod controllers.    Update ts_hexrotcomm, ts_hexapod and ts_rotator accordingly:  * Update the mock controllers to transition to STANDBY instead of whatever it presently transitions to (probably OFFLINE/AVAILABLE).  * Update (probably remove) any comments that describe the old behavior."
Answer: 22502.0

User story: The begin_<state> and end_<state> methods turned out to be a bad idea. Raise deprecation errors when they are used, if possible (this may be a bit tricky, but we could "call if found") and file a ticket for removal.
Answer: 62039.0

User story: "While testing coaddAnalysis I found a small bug in buildTractImage. We are going to take buildTractImage out of the regular running of pipeAnalysis (in DM-22255) but retain the code for possible future use."
Answer: 1216.0

User story: "Bo updated the bending modes and sensitivity matrix for the phosim:    [https://github.com/lsst-ts/phosim_syseng4/pull/1]    He tried to update the related part in ts_ofc:    [https://github.com/lsst-ts/ts_ofc/pull/19]    This task will take over this PR and finish it. This task will fix some minor bugs as well. It is noted that some test cases in ts_MTAOS will need to update as well."
Answer: 20334.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: "Support the DOF (degree of freedom) correction from multiple visits instead of single one. The initial idea now is to use the queue in Model class in ts_MTAOS."
Answer: 36080.0

User story: "Adapt the change of ts_xml 5.0, especially for the MTM2. This task will need to prepare the appropriate software environment for the test. This task will also use the test framework by ts_salobj."
Answer: 8355.0

User story: "As proposed in RFC-682, scikit-image is needed for satellite detection in DM-22221. It will be added to the list of packages in scipipe_conda_env."
Answer: 31692.0

User story: "Depends on [LSST-3228|https://jira.ncsa.illinois.edu/browse/LSST-3228].    Use this to configure a node in the NTS for Felipe to test deploying header service.    _*pup-nts*_ is defined in DNS. Rename this node as _*lsst-devops-ncsa*_ (to follow the same pattern as _*lsst-devops-npcf*_)"
Answer: 67783.0

User story: "Puppet service to apply LSST shared puppet configs on NPCF nodes."
Answer: 10275.0

User story: "Create the initial UX design for the Rubin Observatory search app's front-end (see DM-24298 and linked tickets).    The goals for this design exercise are:   * What types of content are included in the search app?   * How are those types of content categorized and displayed?   * What are the major user groups? What are the key tasks they need to accomplish and how can we streamline those actions?   * How should the site's nav be organized?   * How should search result cards work?    The intent is that this initial design round can get the team onboard with the new search site and set a common vision."
Answer: 17095.0

User story: "This option was added to the argument parser on DM-21849 but not implemented due to problems with dataset deletion."
Answer: 229247.0

User story: "Present status of Broker proposal call to SAC,  converge on new plan in light of COVID-19 and  sample alert packet development status. "
Answer: 60602.0

User story: "requested change:    xxArchiver should listen for largeFileObjectAvailable from xxHeaderService instead of EFD"
Answer: 1462.0

User story: "Add sphinx-click to the Science Pipelines documentation dependencies per RFC-684. Create a new patch release of documenteer."
Answer: 5901.0

User story: "In DM-24350 we sanitized some EFD notebooks to run on nublado hosted at the LDF.  We intended to promote those notebooks to the standard env that all users see, but I hadn't thought through how authentication would be handled in that context.  In order to do that, we need to make a read only user and inject those credentials into user pods at spawn time.  This ticket is to figure that workflow out."
Answer: 80928.0

User story: "Add OPSTN and ITTN series to the legacy [www.lsst.io|http://www.lsst.io/] documentation portal (pre-Algolia search) to service a management request."
Answer: 76.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 PXI simulator are on hold until I obtain network cards from this requisition here [https://cas.aura-astronomy.org/Reqless/en-US/Requisition/ViewRegularRequisition/166724?pendingMyApproval=False].     In the meantime there is a "Crude PXI Simulator" which I will run and configure on a machine <USER>has access to.     -1) Install crude PXI simulator on the server centos machine. This way Russell also has access to the simulator which is the main reason for this task.-    2) -Learn how to operate it, create documentation if needed.-    -3) Identify what is needed so that it can- -interact with newMTMount CSC-
Answer: 26266.0