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 existing Dome {{inPosition}} event has several serious problems:  * It has no boolean flag indicating whether or not the specified device is in position. We need to know "is in position" and "is not in position".  * It has a {{deviceId}} attribute, which badly breaks salobj's ability to automatically output new events only when data has changed. The most recent output is likely to be for a different device! Thus we will get far too many of these events, even when nothing has changed.  * The {{devicePosition}} field is not not useful (especially if you implement DM-25333) and is inadequate for the azimuth (without an associated velocity and time).    I suggest:  * A different inPosition event for each device/axis, e.g.:  * azimuthInPosition(inPosition=True/False)  * elevationInPosition(inPosition=True/False)  * etc.    An alternative is to have one or several events with multiple fields, e.g.:  * inPosition(azimuth=True/False, elevation=True/False, ...)  but it only makes sense to combine data that you get in a single status call. Otherwise you imply information that you don't have!    The same basic problem applies to most other events, including {{motionEnabled}} and {{driveFault}}, {{overTemp}}, {{speedLimitReached}}, {{accelerationLimitReached}} (why do those last two even exist?).  * It would be much better to have a separate event for each device  * We need a flag or other simple way to tell "this condition is present" and "this condition is absent".    Other changes to consider:  * Remove the word {{Change}} from all events that have that suffix. "Change" is redundant. The event is being output *because* the state changed.  * Combine {{lockingPinEngaged}} and {{lockingPinDisengaged}} as {{lockingPin}} with a boolean {{engaged}} flag.  * Combine {{brakeEngaged}} and {{brakeDisengaged}} as {{brake}} with a boolean {{engaged}} flag.  * Combine {{motionEnabled}} and {{driveFault}} into {{driveState}}, with an enum field for enabled/not enabled/fault and another field for the fault code (which is null if enabled/disabled).  * Rename {{interlockAlarm}} field {{interlockAlarmCode}} to {{code}} and look for similar redundancies in other topics. There are a lot of fields that seem needlessly verbose (why "devicePosition" instead of "position", etc.)  
Answer: 2929.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: "On the NTS cluster, Kafka has a small ~50G partition to store its logs, which filled up in about 48h with the CSCs running on the NCSA test stand.    {noformat}  root@cp-helm-charts-cp-kafka-0:/# df -h  Filesystem                   Size  Used Avail Use% Mounted on  overlay                      165G   53G  113G  32% /  tmpfs                         64M     0   64M   0% /dev  tmpfs                         47G     0   47G   0% /sys/fs/cgroup  /dev/mapper/VGsystem-LVvar   165G   53G  113G  32% /etc/hosts  shm                           64M     0   64M   0% /dev/shm  /dev/mapper/VGsystem-LVroot   50G   50G   20K 100% /opt/kafka/data-0  tmpfs                         47G   12K   47G   1% /run/secrets/kubernetes.io/serviceaccount  tmpfs                         47G     0   47G   0% /proc/acpi  tmpfs                         47G     0   47G   0% /proc/scsi  tmpfs                         47G     0   47G   0% /sys/firmware  {noformat}      We have to fine-tune the Kafka broker retention policy to avoid that."
Answer: 22.0

User story: Whenever the Dome CSC is commanded to a new azimuth or elevation, if the command is accepted then it should output a "target" event that gives the details. That way other code, such as the MTDomeTrajectory CSC, can see what's going on.    I suggest these two events (rename as you see fit):  {code}  targetAzimuth:  * position (deg)  * velocity (deg/sec)  * taiTime (unix seconds)    targetElevation:  * position (deg)  * velocity (deg/sec)  * taiTime (unix seconds)  {code}    If we cannot get EIE to give us "move position velocity time" then you may have to ditch the "tai" fields. But I am guessing we can either get that, or something close enough that you can fill out the tai field with at least a reasonable guess.    Once you know what the louver commands will be, I suggest the same sort of event for that data -- and similarly for other systems the Dome controls.
Answer: 3952.0

User story: "The update of the OpSim survey simulation to FBS 1.5 required a new simulated solar system object catalog. This ticket captures generating simulated false detections."
Answer: 6.0

User story: "Technotes are already built with templatebot (the service backing sqrbot-jr create project). We should further extend the service for change controlled documents and test reports which are principally maintained in DocuShare, but also have drafts available from LSST the Docs (the PDFs from LTD are often used populating DocuShare). The key difference is that these documents have pre-assigned handles from DocuShare.   * For regular change controlled documents, we can use the templates established in lsst/lsst-texmf.   * For test reports DMTR, I think the request is to have a minimal template with the build infrastructure since the bulk of the DMTR content generation is done with a tool called docsteady."
Answer: 9918.0

User story: Sometimes the spawner hangs for a long time.  It seems to, perhaps, be something to do with a kubernetes client bug?  "Involved object cannot be None"
Answer: 15684.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: "Fix the typing errors and get the build working with some refactors.  Then work on the deploying more."
Answer: 13121.0

User story: "In DM-25325 I updated base.Packages to allow YAML format to be written. Now I need to change daf_butler to write them out in YAML and obs_base to check that butler can read them properly.    I've added YAML representers so that a simple change to the formatters config yaml to use YamlFormatter should do it. We could also use a specialist formatter that knows how to do read/write with writeParameters controlling the file format..."
Answer: 6129.0

User story: "Now that Jenkins is producing centos7 and 8 binaries, newinstall shall be able to deploy them.     In order to be consistent, centos6 shall be removed  and centos8 shall be added."
Answer: 121.0

User story: "We currently write Packages out as Pickle but we would prefer to write them out as YAML."
Answer: 349.0

User story: "We seem to have defaulted to writing PropertySet/List in pickle format in gen3 even though it's using YAML in gen2. Switch to YAML and add a quick test in obs_base."
Answer: 245.0

User story: "Make some CI Logon tokens and get them set up for gafaelfawr just in case we need them.  Also it would be good to get away from the name nublado, since it's just an overloaded term."
Answer: 5896.0

User story: "1. docstrings for define_visits and ingest_raws are missing so {{butler --help}} displays not-useful information for these commands    2. change {{butler register-instrument}} so that {{instrument}} is an arg instead of an opt {{butler register-instrument REPO lsst.obs.lsst.Latiss}} (without the -i). It should take multiple values for INSTR.    3. If obs_base is set up such that a commands yaml is found but obs_base is not importable, {{butler --help}} falls over in a big heap. I think we should protect the doImport in {{cmd = self.get_command(ctx, subcommand)}} and issue a {{“could not import sucommand X”}} warning but continue on.    4. in {{butler --help}}, sort the commands alphabetically"
Answer: 8976.0

User story: "According to Andy there may be power up Activities from IT happening Julio. This task is to coordinate / fact find what needs to be accomplished to bring up the HexRot & M2 servers back online. "
Answer: 20053.0

User story: Jobs that use newinstall are failing when the miniconda already exists.    Previously, when a miniconda path already existed, even if a user was prompted to install it or it was assumed to install it via the {{-b}} option, an installation was not attempted and it was assumed to use that miniconda installation.    Changes from DM-24972 assumed that the miniconda path does not exist if a user asks to install it, either by typing "yes" interactively or using batch mode. 
Answer: 4384.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 a component of the Environment Awareness System EAS ([https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73574873),|https://confluence.lsstcorp.org/pages/viewpage.action?pageId=73574873)] it's necessary to develop a dome environment conditioning system, to control the temperature during daytime."
Answer: 20082.0

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

User story: "Document the track simulation in rotator Simulink model. This is a follow-up task of DM-25045 to summarize and analyze the test results."
Answer: 5930.0

User story: "Health & Status data are routed in FPGA through the Request queue. The 64bit data are then squeezed into 4 16bit Response FIFO values. This design is suboptimal for two reasons:   * response queue is also used to send Modbus responses from ILCs, the mix effectively prevents multi-threading on CPU (Host) side to query H&S data and responses at the same time   * as H&S data are mixed with responses, it's hard to tell which data on reposne queue are from H&S and which are from ModBus - that is probably reason why vital H&S collection was implemented in FPGA, but not in C/C++ controller (where it most likely never worked)"
Answer: 6286.0

User story: "New docker images are needed for the HS using   HeaderService: 2.2.1  salobj: v5.14.0  idl:v1.2.0  xml:v5.1.0   sal: 4.1.1"
Answer: 616.0

User story: "The Docker container and virtualbox are working and running. This task is to;    * Configure the HMI running on the Docker container to point to the NSV's within the virtualbox.   * Show that the EUI is displaying values correctly."
Answer: 81415.0

User story: "Backup of the NTS EFD complete.    New storage classes {{local-path}} and {{nfs-path}} were created on the NTS cluster allowing us to redeploy Kafka, Chronograf and Kapacitor using {{local-path}} and redeploy InfluxDB using {{nfs-path}}.    We'll proceed with the redeploy and move data over from the old pvs to the new pvs."
Answer: 5302.0

User story: "Users want newer RC2 runs converted.   While waiting for the current RC2 run to finish, test the code using w_2020_22 stack with RC2 w_2020_19."
Answer: 45771.0

User story: "The HVAC SAL topic names are deduced from the Spanish MQTT topic names where special characters have been replaced with Spanish descriptions of those special characters. This leads to overly long topic names like    HVAC_lsstBarraoblPiso01BarraoblTccGuionP1GuionSalaGuionMaquinas    Come up with a naming convention such that those long topic names can be made much shorter and still can uniquely be converted from the SAL topic names to the MQTT topic names and back. Then implement that in both ts_xml and ts_hvac."
Answer: 57374.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: "Work with Tiago to create a workflow where the daily RPM job will trigger the BaseDevImage job, which will kick off the SalObj Container job, which, in turn, will trigger the DevEnv job.  The artifacts from the DevEnv job can be junked; we only want feedback on the status and stability of the dependencies of the DevEnv."
Answer: 19145.0

User story: "Doing this will make the determination of canonical URLs for various internal services easier."
Answer: 5778.0

User story: "[~<USER> has discovered that I messed up the comCam instrument name when I normalized them in DM-23980. I ended up with LSSTComCam in the gen3 instrument and LSST-ComCam in the metadata translator.    Standardize on LSSTComCam to match LSSTCam."
Answer: 4169.0

User story: "The naming of the folder with the templates for the HeaderService changed when adding ComCam support, but the {{setup.py}} failed to capture this and therefore the conda packages are now faulty."
Answer: 4188.0

User story: "Adds generating and use of deps files for cpp source files to libM1M3.a target."
Answer: 1.0

User story: "Update the builds of OpenSplice (rpm's and ts_opensplice) to the   latest version from the community edition github repo"
Answer: 14331.0

User story: "Keeping the fakes insertion code up to date with changes to calibrate and config files is going to be difficult given the current setup. The plan is to refactor the code to make this easier."
Answer: 24740.0

User story: "Remy Joseph noticed that in scarlet residuals there appeared to be a problem fitting the center of galaxies:     !Screen Shot 2020-06-04 at 12.23.24 AM.png|thumbnail!     This ticket tracks work done by myself to assist Remy and <USER>to identify the cause of the behavior and determine if there is something broken in either our constraints or optimization algorithm used in scarlet."
Answer: 193.0

User story: https://ci.lsst.codes/blue/organizations/jenkins/scipipe%2Flsst_distrib/detail/lsst_distrib/1021/pipeline    {code}  ../../miniconda/envs/lsst-scipipe-1a1d771/lib/python3.7/site-packages/py/_path/local.py:701:  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _  from .version import *  from .association import *  from .diaForcedSource import *  from .mapApData import *  from .afwUtils import *  from .diaCalculation import *  from .diaCalculationPlugins import *  from .loadDiaCatalogs import *  > from .packageAlerts import *  python/lsst/ap/association/__init__.py:30:  _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _  __all__ = ("PackageAlertsConfig", "PackageAlertsTask")  import os  import lsst.afw.fits as afwFits  > import lsst.alert.packet as alertPack  E ModuleNotFoundError: No module named 'lsst.alert'  {code}    This will break tonight's nightly build unless we get a quick fix in soon.
Answer: 145.0

User story: "Build command-line tool to do table generation based on results of research in DM-25264"
Answer: 1.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: "Generate tables such that their contents correctly match the data model and are internally consistent (i.e. ForcedSources are correctly linked to Objects and Visits)"
Answer: 1.0

User story: Placeholder ticket so P6 upload will notice this "Won't Fix" epic.
Answer: 1.0

User story: "Keep up with Tiago's recommendations for sal-sciplat-lab."
Answer: 35275.0

User story: "In the Dome Software Meeting of 2020-06-04 new JSON-based command and configuration protocols were agreed upon, as well as new LLC states and statuses. This ticket is to make the necessary changes to the Dome CSC and mock controller to adopt those changes.    Protocol details, with mention to the response codes, can be found here    https://confluence.lsstcorp.org/display/LTS/Command+and+Configuration+Protocols"
Answer: 9948.0

User story: "The rotator Simulink model should be able to track multiple targets. The system will fail/ crash if there are targets that have different directions. In addition, sometimes, the simulation will fail even though all targets are in the same direction. This task will dig into the Simulink model to see how is fitting of multiple targets.    The following figure demonstrates the failure. The x-axis is the time in second and the y-axis is the value such as the rotation position in degree. There are two targets with positions of +1.5 and -1.5 degree. The simulation time is 30.1 seconds and the simulation crashes in the middle with zero-crossing error.      !trackErrorForTargetsWithDifferentDirections.png|thumbnail!"
Answer: 28716.0

User story: "The general idea is that you can use a Faust agent to process messages from a given Kafka topic and add those messages to a Faust table for persistence. The table is configured as a tumbling window. The window configuration parameters are the window size and the expiration time. When the window expires a callback function is called to process the messages in that window. That's when the aggregation happens and when a new Kafka topic is produced with the aggregated values.    In a previous ticket DM-24600 we created Faust records dynamically which saved us from generating static code for the models in Faust.    After some investigation, we concluded that it would be difficult to create the agent's code at runtime.  We'll try the approach of generating the code for the agents from a template and use Faust auto-discover mechanism to import the corresponding modules."
Answer: 18867.0

User story: "Modify [a copy of] the gen3-hsc-rc2 bootstrap.py script that can convert the outputs of one or more standard RC2 processing runs.    This should just be a matter of updating the configured dataset types and passing Rerun arguments to ConvertRepoTask.run, and then inventing an interface that allows the user to specify which processing runs to convert.  "
Answer: 11371.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: "If the rotator does not receive the track command for a long time, the rotator should be put into the Fault state. This could be 0.5 second (by Tiago) or 1 second (by Russell). At this moment, we do see this in the Simulink model by the simulation experiment, but we do not know how that is decided. In addition, we did not see this when we did the test on summit. This task needs to figure out what is the existed logic in model and how to update it.    The following is the figure to show the simulation result (detail is at DM-25243):    !track_v0_1_long_enterFault.png|thumbnail!    The system is at the Fault state around time equals 20.2 seconds (no new track command after time=6 seconds)."
Answer: 25748.0

User story: "The path generator will continuously update the demand position even if there is no new track command received in the SlewAndTrack sub-state. The initial suspect is that this comes from the non-zero target velocity in the final received track command. This will continue to update the position command. The initial idea to fix this is to reset the velocity command to be zero if no new track command received.    The following figure (x-axis: time in seconds, y-axis: value such as position in degree) shows this problem. There are two targets (positions = 1.2 degree and 3 degree. velocity = 0.01 deg/sec and -0.01 deg/sec). The track command does not continue after the time equals 6 seconds. We could see the rotator position is at 3 degree when time is at 8 seconds but the demand position is decreasing after time=8 seconds (rotator's position keeps the same) because of the second target has the velocity of -0.01 deg/sec.    !track_v0_1_long_enterFault.png|thumbnail!     "
Answer: 18816.0

User story: "Create new Ad-hoc repos (not synced by Pakrat):  v4.2.3-22 (what we'll have to use for test systems, e.g., latest kernel compatibility, etc.)  v5.0.5-0 (what we'll actually use for the PM)"
Answer: 105.0

User story: "Take the object table parquet files at   /datasets/hsc/repo/rerun/RC/w_2020_19/\*/deepCoadd-results/merged/\*/objectTable-\*.parq  as inputs, go through the workflow and ingest into Qserv.      "
Answer: 62316.0

User story: "Create XML for AdamSensors (formerly pressureSensor) CSC. This will basically just be telemetry topics for temperature and pressure readings on the ADAM's 6 potential analog channels. "
Answer: 15709.0

User story: "Getting the quantum database representation stable and future-proof requires more thought than we want to put into it before gen2 deprecation, so this ticket is a near-term replacement for DM-24613, which we'll pick up again later.  See also https://lsstc.slack.com/archives/C2JPT1KB7/p1591284060371700    Preliminary plan is to remove the quantum and dataset_consumer tables, along with the dataset.quantum_id column.  It'll be easier to add those back in than alter them to match what we do in the future."
Answer: 448.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "LTD Dasher has typically displayed a link to the CI dashboard page for a project. However, now that we're using many types of CI systems (GitHub Actions, Jenkins, Travis CI), we can't assume the CI service. Until we modify the LTD Keeper API to let an uploader specify the CI link, we should just omit this information."
Answer: 261.0

User story: "In DM-24992 we released Lander 0.2, which supports deployments from GitHub Actions. That version also uses the new release of LTD Conveyor, which supports uploads with AWS credentials. Meanwhile, ReStructuredText technical notes should start using LTD Conveyor directly.    The purpose of this story is to migrate the templates for technical notes to now use GitHub Actions and AWS credential-less uploads to LSST the Docs.    Specific steps are:   # Add LTD_USERNAME and LTD_PASSWORD secrets to each participating GitHub organization. In turn, create an upload-only LTD account for each organization.   # Update the templates in lsst/templates with the new GitHub Actions-based workflow.   # Update the post-processing hooks in lsst-sqre/lsst-templatebot-aide to no longer register the technote repo with Travis and no longer send the configuration PR."
Answer: 6271.0

User story: "Send bits aren't reported from FPGA. The reason is unknown."
Answer: 12794.0

User story: "This ticket is to produce a final sample of alerts for community brokers that incorporates pipeline improvements since DM-24941."
Answer: 46935.0

User story: "This ticket is to draft a brief explanatory README to accompany the sample alerts distributed to the community brokers and science collaborations.  It should provide pointers to appropriate documentation and describe limitations and omissions relative to the planned Rubin alert packets."
Answer: 58844.0

User story: "In preparation for the June PM, I'd like to get the following new YUM repos mirrored:   * duosecurity - [https://pkg.duosecurity.com/CentOS/7/x86_64]   * ius - [https://repo.ius.io/7/x86_64]"
Answer: 1476.0

User story: "Release blockers which were merged after w_2020_22 need to be backported to an appropriate branch to support release 20.    Issues are:    - DM-25177  - DM-25184  - DM-25187  - DM-25210"
Answer: 807.0

User story: "Now that CentOS is running on the RPi4, reinstall it and document all steps. The document can be found at    [https://confluence.lsstcorp.org/display/LTS/Installation+instructions+CentOS+7+on+Raspberry+Pi+4]"
Answer: 3131.0

User story: "In Jenkins overnight: https://ci.lsst.codes/blue/organizations/jenkins/scipipe%2Fap_verify/detail/ap_verify/596/pipeline"
Answer: 26.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: "Prepare and test older servers in NCSA 3003 that are configured from lsst-pup Puppet server. Currently we know the following needs to be prepared and tested:   * Upgrade to CentOS 7.8   * Update other YUM repo pakrat snapshots to ~2020-06-10   * Confirm docker is updated   * Remove older SCL packages from Dev servers   * Update duo YUM repo to point to lsst-repos01   * Test Dell firmware upgrades?    The list of test servers have traditionally been:   * lsst-dts   * lsst-l1-cl-frwd12   * lsst-l1-cl-frwd13   * lsst-l1-us-failfm   * lsst-nts-acamfwdr2   * lsst-nts-ccamfwdr2   * lsst-nts-ccs1   * lsst-test1   * lsst-test4   * lsst-test5   * lsst-test6   * lsst-test7   * lsst-test8    But we should confirm L1 & NTS servers with Felipe before testing."
Answer: 11739.0

User story: "The deployment of the T&SS has now fully migrated to miniconda.  New docker images should be built and tested using the new install."
Answer: 7217.0

User story: "The deployment of the T&SS has now fully migrated to miniconda.  A new sanctioned recipe to install the software on the NCSA Test Stand needs to be developed and Tested."
Answer: 7228.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: "DRP metrics regressions in w19 turned out to be the result of multiple issues. After fixing the overscan issue, we noticed the the metrics still did not return to their w14 baseline.     The lingering problem was isolated to an interaction between {{psfex}} and the new conda env. I don't understand exactly why, but stepping through pdb with a w18 and w17 showed that despite giving psfex the same inputs we were getting different answers here:  {code}  > /software/lsstsw/stack_20200504/stack/miniconda3-4.7.12-2deae7a/Linux64/meas_extensions_psfex/19.0.0-  2-gd82b0d5+3/python/lsst/meas/extensions/psfex/psfexPsfDeterminer.py(385)determinePsf()  -> psfex.makeit(fields, sets)  {code}  And inspection of fields yielded segfaults in w18.    **To reproduce:**  {code}    singleFrameDriver.py /datasets/hsc/repo --calib /datasets/hsc/repo/CALIB/ --rerun private/<USER>RC2/w22reg/hybrid --id visit=1208 ccd=89 --cores 1 --config processCcd.isr.doWrite=True  {code}     For iter 1 you should see {{singleFrameDriver.processCcd.charImage.measurePsf INFO: PSF determination using 65/70 stars}}  as a success marker.    {code}  [<USER>lsst-dev01 w22reg]$ diff w17_ccd89.log  w18_ccd89.log  | grep PSF  < singleFrameDriver.processCcd.charImage.measurePsf INFO: PSF determination using 65/70 stars.  < singleFrameDriver.processCcd.charImage INFO: iter 1; PSF sigma=1.23, dimensions=(41, 41); median background=2387.68  > singleFrameDriver.processCcd.charImage.measurePsf INFO: PSF determination using 45/70 stars.  > singleFrameDriver.processCcd.charImage INFO: iter 1; PSF sigma=1.11, dimensions=(41, 41); median background=2387.68  < singleFrameDriver.processCcd.charImage.measurePsf INFO: PSF determination using 64/74 stars.  < singleFrameDriver.processCcd.charImage INFO: iter 2; PSF sigma=1.23, dimensions=(41, 41); median background=2387.75  > singleFrameDriver.processCcd.charImage.measurePsf INFO: PSF determination using 50/74 stars.  > singleFrameDriver.processCcd.charImage INFO: iter 2; PSF sigma=1.11, dimensions=(41, 41); median background=2387.82  {code}    For more info see  team debugging June 2 2020 here: https://lsstc.slack.com/archives/C4JQP6FRS/p1591113943137300"
Answer: 121.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: {{python -m pytest .}}  does not succeed on the master branch of github.com/lsst/alert_packet, at least for me working locally. We should fix this.    The error I get is this:    {code}  ======================== test session starts =========================  platform linux -- Python 3.8.2, pytest-5.4.3, py-1.8.1, pluggy-0.13.1  rootdir: /home/<USER>code/rubin/alert_packet  collected 6 items                                                        test/test_io.py .                                              [ 16%]  test/test_schema.py ..                                         [ 50%]  test/test_schemaRegistry.py .                                  [ 66%]  test/test_schemas.py F.                                        [100%]    ============================== FAILURES ==============================  ______________ SchemaValidityTestCase.test_example_avro ______________    self = <test.test_schemas.SchemaValidityTestCase testMethod=test_example_avro>        def test_example_avro(self):          """Test that example data in Avro format can be loaded by the schema.          """          no_data = ("1.0",)  # No example data is available.          bad_versions = ("2.0",)  # This data is known not to parse.                for version in self.registry.known_versions:              path = path_to_sample_data(get_schema_root(), version,                                         "fakeAlert.avro")              schema = self.registry.get_by_version(version)                    if version in no_data:                  self.assertFalse(os.path.exists(path))              else:                  with open(path, "rb") as f:                      if version in bad_versions:                          with self.assertRaises(RuntimeError):                              schema.retrieve_alerts(f)                      else:                          retrieved_schema, alerts = schema.retrieve_alerts(f)  >                       self.assertEqual(retrieved_schema, schema)  E                       AssertionError: <lsst.alert.packet.schema.Schema object at 0x7f189cd8c940> != <lsst.alert.packet.schema.Schema object at 0x7f189cd14b50>    test/test_schemas.py:77: AssertionError  ====================== short test summary info =======================  FAILED test/test_schemas.py::SchemaValidityTestCase::test_example_avro  ==================== 1 failed, 5 passed in 0.29s =====================  {code}     
Answer: 50373.0

User story: The Generics field of ts_xml/sal_interfaces/SALSubsystems.xml, will define which Generic topics the CSC is using.  It will either be "yes" if it uses them all, or a comma-delimited list of specific topics.  This requires adding some infrastructure to the suite generators.    Also, there should be an XML unit test to verify this field is either yes, or contains valid topic values.
Answer: 42405.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 star galaxy classifier has bit rotted from not being touched for ages. Now that making object tables is in pipe tasks the classifier will be more easily usable, as it runs on top of the object tables. Make it work again before testing it and moving it to pipe_tasks."
Answer: 18593.0

User story: "DM-25179 introduces some breaking changes to ts_simactuators. Update other code accordingly."
Answer: 1.0

User story: "DM-25179 introduces some breaking changes to ts_simactuators. Update other code accordingly."
Answer: 3008.0

User story: "This sprint includes 3+ releases, SAL v4.1.3, SAL v4.1.4 and XML v6.0.  This task covers the time necessary to process the releases and deal with any fallout or issues that result.     Also, the XML 6.0 release will be built against SAL v4.1.1.  The current build harness isn't quite ready to build against an older version, so this task will also cover the work to update the build accordingly."
Answer: 4329.0

User story: "Adds generating and use of deps files for cpp source files to libM1M3.a target."
Answer: 2900.0

User story: "Fix up whatever we need to be able to roll out nublado.lsst.codes in the new way."
Answer: 28940.0

User story: "Autodetection of network interfaces fails for SAL containers with multus interfaces.    I have a slapdash workaround.  We should have a better one.  "
Answer: 2998.0

User story: "lsst.alert.packet is a dependency of lsst.alert.stream, so it needs to go on PyPI too for DM-25102."
Answer: 12927.0

User story: "The Kafka producer Helm chart needs to have the WAIT_ACK environment variable added to the list of configurables."
Answer: 1175.0

User story: "Update the CSC documentation templates so make them ready for packaging/distribution.     "
Answer: 3044.0

User story: "make Registry.queryCollections callable by a butler command    output should use yaml syntax, so something like:  {code}collections:  - collection1  - collection 2  {code}  and similar for Registry.getDatasetTypes "
Answer: 5847.0

User story: "We have recently been noticing delays in Travis communiction. We have been given permission to switch daf_butler to GitHub actions as a test bed.    To simplify dev guide documentation later we have been advised to do flake8 in one workflow and mypy in a second."
Answer: 215.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 azimuth rotation doesn't handle the 0/360 azimuth and 0/90 elevation boundaries at all. It will just move to negative (in case of the 0 boundary) or too large (in case of the 360 and 90 boundaries) values. Please fix."
Answer: 191252.0

User story: "Add the ability to M1M3cli app to send Modbus commands to ILC. That will enable execution and debugging of connections with ILCs."
Answer: 10666.0

User story: "Pull in nginx-ingress in the same way I've done the other services, to allow for per deployment configuration of nginx"
Answer: 1202.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: "Write a scanner that will determine versions in use for a SQuaRE repository. For the initial implementation, support:    - Helm charts  - Kustomize chart references  - Python make init  - Docker images in Helm charts  - GitHub actions  - pre-commit hooks"
Answer: 54842.0

User story: "Documentation is needed to describe adding credentials to segwarides.  It is essentially just executing {{vault kv patch}} with the correct paths and data, but still needs to be written down concretely."
Answer: 3973.0

User story: "[On GitHub|https://github.com/lsst-dm/dm_dev_guide/issues/404], Archit reports:    {quote}  It seems, the function: {{friend std::ostream& operator<<(std::ostream&, ExampleOne const&);}} is not wrapped in the example given: https://github.com/lsst dm/dm_dev_guide/blob/master/pybind11/how-to.rst  {quote}"
Answer: 514.0

User story: It would be very helpful for the OODS if butler recorded ingest time as well as observation time. Storing ingest time and allowing queries such as "give me all datasets in this collection that were stored more than N days ago" would significantly streamline OODS data expiry. The returned refs could immediately be passed to pruneDatasets.  Currently OODS works by going behind gen2 butler's back and deleting the files directly from datastore without involving butler.
Answer: 204450.0

User story: "In order to implement DM-13353 we need to be able to specify parameters in datastore configs associated with the write formatters.    We must assume that parameters are never required for reading with a formatter since that would break our contract with the user that any change to configuration of a datastore should not break the ability to read a file."
Answer: 4562.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: e.g. https://ci.lsst.codes/job/sqre/job/infra/job/documenteer/883/console:    {code}  [autosummary] generating autosummary for: getting-started/coaddition.rst, getting-started/data-setup.rst, getting-started/display.rst, getting-started/index.rst, getting-started/multiband-analysis.rst, getting-started/photometry.rst, getting-started/processccd.rst, index.rst, install/demo.rst, install/docker.rst, ..., releases/v13_0_qserv_dax.rst, releases/v13_0_sui.rst, releases/v14_0.rst, releases/v15_0.rst, releases/v16_0.rst, releases/v17_0.rst, releases/v18_0_0.rst, releases/v18_1_0.rst, releases/v19_0_0.rst, tasks.rst    Traceback (most recent call last):    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/documenteer/sphinxrunner.py", line 84, in run_sphinx      warningiserror, tags, verbosity, jobs)    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx/application.py", line 233, in __init__      self._init_builder()    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx/application.py", line 311, in _init_builder      self.emit('builder-inited')    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx/application.py", line 444, in emit      return self.events.emit(event, self, *args)    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx/events.py", line 79, in emit      results.append(callback(*args))    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx_automodapi/automodsumm.py", line 255, in process_automodsumm_generation      lines = automodsumm_to_autosummary_lines(sfn, app)    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx_automodapi/automodsumm.py", line 327, in automodsumm_to_autosummary_lines      filestr = automodapi.automodapi_replace(fr.read(), app, True, docname, False)    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx_automodapi/automodapi.py", line 277, in automodapi_replace      modnm, toskip, onlylocals=onlylocals)    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx_automodapi/automodapi.py", line 388, in _mod_info      for localnm, fqnm, obj in zip(*find_mod_objs(modname, onlylocals=onlylocals)):    File "/j/ws/sqre/infra/documenteer/doc_template/home/.local/lib/python3.7/site-packages/sphinx_automodapi/utils.py", line 78, in find_mod_objs      __import__(modname)  ModuleNotFoundError: No module named 'lsst.daf.butler.core.safeFileIo'  {code}
Answer: 102.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: "RC2 reprocessing with w_2020_22         Tasks done:   * makeSkyMap   * singleFrameDriver   * jointcal   * skyCorrection   * coaddDriver   * multiBandDriver   * forcedPhotCcd   * visitAnalysis   * compareVisitAnalysis   * coaddAnalysis   * colorAnalysis   * compareCoaddAnalysis   * matchVisits   * dispatch_verify_colorAnalysis   * matchedVisitMetrics     * dispatch_verify_matchedVisit     * validateDrp     * writeObjectTable     * transformObjectCatalog     * consolidateObjectTable     * consolidateSourceTable"
Answer: 23089.0

User story: When ingesting/processing {{phosim}} data, one encounters the following messages:  {code:python}astro_metadata_translator.observationInfo WARN: Ignoring Error calculating property 'temperature' using translator <class 'lsst.obs.lsst.translators.phosim.LsstPhoSimTranslator'>: "Could not find ['TEMPERA'] in header"  astro_metadata_translator.observationInfo WARN: Ignoring Error calculating property 'pressure' using translator <class 'lsst.obs.lsst.translators.phosim.LsstPhoSimTranslator'>: "Could not find ['PRESS'] in header"  astro_metadata_translator.observationInfo WARN: Ignoring Error calculating property 'boresight_airmass' using translator <class 'lsst.obs.lsst.translators.phosim.LsstPhoSimTranslator'>: "Could not find ['AIRMASS'] in header"  LsstCamAssembler WARN: argDict[boresightAirmass] is None; stripping  {code}  If {{phosim}} is never going to give us weather it would be good make the translator use nominal defaults to and not complain about it.
Answer: 27078.0

User story: "This document will be the basis for evaluating possible options, and if we implement components internally, the initial requirements for that implementation."
Answer: 67867.0

User story: The Kafka producers should place a file in /tmp called RUNNING right after log statement says "Running". This will allow the use of a readiness probe in the k8s deployment so that pod teardowns don't start until the next producer pod is ready.
Answer: 64691.0

User story: "Create methods to load and pack diaForcedSources into alert packets as part of DiaPipe and PackageAlerts tasks."
Answer: 37584.0

User story: "Per RFC-699, we'll be using astropy.CCDData to serialize cutouts for alert packets. Please take a look at the Astropy docs (https://docs.astropy.org/en/stable/api/astropy.nddata.CCDData.html#astropy.nddata.CCDData) and figure out how to create them from our Exposure objects."
Answer: 28889.0

User story: "Currently, we avoid calling the service from the tests since it does not have the credentials we need for the tests.  It would be good to spin a local segwarides instance with the correct test credentials."
Answer: 8761.0

User story: "Some LVV elements have inconsistent priorities set in the header information, e.g    https://jira.lsstcorp.org/browse/LVV-72   https://jira.lsstcorp.org/browse/LVV-42    LVV-177    The 'Details' section says '1a' and the 'Requirement details' section says '1b'    These should be corrected and all DM LVV checked for consistency"
Answer: 34847.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 ticket is to benchmark direct vs fft convolution methods and compare them against MultiProFit's Gaussian mixture evaluation with analytic convolution."
Answer: 4298.0

User story: In DM-23980 I standardized the instrument class names for Gen3. Doing so means that both {{lsst.obs.lsst.LsstCam}} and {{lsst.obs.lsst.instrument.LsstCam}} work. Since we don't want multiple ways of specifying the same instrument and we already know of cases where people think they need to include the {{.instrument}}, rename the internal {{instrument.py}} to {{_instrument.py}} to make it clearer that this name should not be used.    One caveat is that when we register the instrument we call getFullTypeName so if you specify the short name the registry still sees the full name and we therefore have to promise not to move that class later inside the package. One solution to that is for the instrument class to not use getFullTypeName but to "know" the public name of itself.
Answer: 481.0

User story: "[~<USER> has discovered that butler ingest-raws does not work with LSST data because the metadata translators have not been registered. It seems the tests are passing because other tests import the translators.    I think a generic fix is to preimport all registered instrument classes before running the ingest itself.  This would cause all metadata translators to be imported. All these classes should exist."
Answer: 317.0

User story: "Click only supports --help out of the box. It provides guidance about how to support {{-h}} at https://click.palletsprojects.com/en/7.x/documentation/#help-parameter-customization.  this will need to be done for {{butler -h}} and {{butler <subcommand> -h}}"
Answer: 5562.0

User story: "This ticket is to implement a wavelength focus dependence in the ATAOS. The information is already being published by the ATSpectrograph and the XML is in place in the ATAOS, but the functionality remains to be implemented."
Answer: 180906.0

User story: "ISR is w18  is causing strange features, likely caused during DM-23396. It only affects some CCDs which is why we didn't see problems in Jenkins runs.  One such bad CCD is   visit=23718 ccd=66.    How to reproduce:  singleFrameDriver.py /datasets/hsc/repo --calib /datasets/hsc/repo/CALIB/ --rerun /path/to/your/rerun --config processCcd.isr.doWrite=True --id visit=23718 ccd=66 --cores 1    Other bad CCD's can be found by visualizing the calexps in RC/w_2020_19/DM-24822-sfm or looking at the compareVisit plots in pipe_analysis: e.g. https://lsst-web.ncsa.illinois.edu/~<USER>w_2020_19_qaPlots/HSC-R/tract-9813/visit-23718/compareVisit-v23718-diff_base_PsfFlux_apCorr-sky-gals.png  https://lsst-web.ncsa.illinois.edu/~<USER>w_2020_19_qaPlots/HSC-I/tract-9813/visit-19698/compareVisit-v19698-diff_base_CircularApertureFlux_12_0-sky-gals.png   "
Answer: 1412.0

User story: "Write a brief technote describing recent progress in understanding and planning for image differencing in advance of the meeting with Robert on 2020-06-16."
Answer: 45804.0
give resolution time in minutes for the given user story, only provide the number of minutes in the output without any other text

User story: "DM-23179 accidentally removed the HSC-R and HSC-R2 colorterms."
Answer: 283.0

User story: "There is only about a minute between the end of the RPM Daily Build and the start of the IDL_Conda job.  This isn't quite enough time for the yum repo to finish indexing all the new RPMs, so the IDL job often fails as a result.  Figure out a way to have the IDL job wait until the desired RPM is available before trying to install it."
Answer: 7628.0

User story: "This is a big task for this sprint to wrap lots of bits and pieces of work on the pressuresensor CSC, rename it to AdamSensors, and be done with it for a long time."
Answer: 76217.0

User story: "In the weekly Dome Software Meeting of 2020-05-28 it was decided to replace YAML with JSON when sending commands from and receiving replies in the Dome CSC. This ticket will take care of that and will also make sure that there will be a central function to construct the commands (in the Dome CSC) and replies (in the mock_controller simulator) that does this so a possible future technology switch could be done more easily."
Answer: 10183.0

User story: "This will require a single line Puppet branch, along with some kubectl commands."
Answer: 5722.0

User story: SAL CPP (and probably Java) bindings outputs "createWriter: " kind-of-debug messages to cout. Look for "createWriter in lsstsal/scripts/code/templates/SALDDS.cpp.template ( I deleted the lines) in attached dif.[^d] Please either remove those poluting lines, make them to print to stderr, or even best feed them to some logging so those can be controlled from CLI/application. I am using spdlog in M1M3 SS and will not object in integrating those messages with spdlog logging.
Answer: 197415.0

User story: "It's been advantageous to have an OODS environment within a container without having the OODS itself running so that new versions of the OODS can be tested.  I've created this a number of times now, so I think it's worthwhile to just add it to the repo."
Answer: 8588.0

User story: "Do a standard reprocessing of HiTS2015 with ap_pipe with the latest weekly. The results will land on lsst-dev in {{/project/<USER>hits2015/rerun/cw_2020_06}}. "
Answer: 71335.0

User story: "Change the SAL generated rpm naming convention to support the scheme outlined in https://confluence.lsstcorp.org/display/LTS/Proposal%3A+RPM+naming+convention+change"
Answer: 30339.0

User story: "Take the ESS sources from GitHub and install them in a RPi4 that is prepared with the SAL software stack. Also make sure that the software gets started at system start up."
Answer: 8751.0