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: "Assign the OFC (Optical Feedback Control) state0 in ts_MTAOS by configuration file. The *ConfigurableCsc* class in ts_salobj is the basic CSC (Commendable SAL Component) class for the subsystem such as *MtaosCsc* in ts_MTAOS to use. The configuration file is located at MTAOS directory of ts_config_mttcs. The following document explains the details of this: [TSTN-017|https://tstn-017.lsst.io/]. When writing the configuration file, a schema is needed to verify the configuration file based on: [Write a CSC|https://ts-salobj.lsst.io/salobj_cscs.html#writing-a-csc].    OFC is the component that calculates the correction of mirror bending mode and hexapod position. The control algorithm in use can follow [Real time wavefront control system for the Large Synoptic Survey Telescope (LSST)|https://drive.google.com/file/d/1RyMQWeXWRZLtxM8KkSwtB3STzMM9fCvX/view?usp=sharing] and [Control Algorithm in Optical Feedback Control|https://confluence.lsstcorp.org/display/LTS/Control+Algorithm+in+Optical+Feedback+Control]. The state0 (*s*~*0*~ in the [Control Algorithm in Optical Feedback Control|https://confluence.lsstcorp.org/display/LTS/Control+Algorithm+in+Optical+Feedback+Control]) is an intentional parameter used in *x00* reference, which is explained in the above links.    The AOS software contains the simulation code and control code. For the simulation, the user needs to use the repos: ts_wep, ts_ofc, and ts_phosim. For the control code, the user needs to use the repos: ts_wep, ts_ofc, and ts_MTAOS. The ts_phosim is not needed in the control and the ts_MTAOS is not needed in the simulation. In this task, we focus on the control code.    The followings are the steps in this task:   # Update the [default.yaml|https://github.com/lsst-ts/ts_config_mttcs/blob/develop/MTAOS/v1/default.yaml] in ts_config_mttcs to contain the state0 information as the following: [state0inDof.yaml|https://github.com/lsst-ts/ts_ofc/blob/master/policy/comcam/state0inDof.yaml]. I prefer to have two yaml files (default.yaml + state0inDof.yaml) instead of one (default.yaml) in ts_config_mttcs. However, we need to check ts_salobj can support this or not.   # Provide the related schema: [MTAOS.yaml|https://github.com/lsst-ts/ts_MTAOS/blob/master/schema/MTAOS.yaml] in ts_MTAOS/schema directory. Prefer to have two files instead of one. But this depends on the implementation of ts_salobj.   # Update *MtaosCsc* class in ts_MTAOS to read the configuration of state0. *MtaosCsc.configure()* will read the configuration file from SAL. *ConfigByObj* and *ConfigByFile* classes inherit from *ConfigDefault* to read the data. We need to update the related test cases to make sure the *MtaosCsc* can change the state0 by SAL or file.   # Override the default state0 when *OFCCalculation* is instantiated by *OFCCalculationFactory.getCalculator()* in *Model.ofc*. The state0 is stored in the internal data of *Model.ofc.ztaac.optCtrl*. The developer can do *OFCCalculation.getZtaac()* to get the *ztaac* attribute. After this, the developer can use *ZTAAC.setState0()* to set the state0 values. The related *get()* functions are provided for the test. By default, the state0 is set by *OFCCalculation()* --> *OFCCalculation._configZTAAC()* --> *ZTAAC.setState0FromFile()*. It is noted that we will keep the default state0 file in ts_ofc for the simulation (the AOS simulation does not know the ts_MTAOS. The UW team is using the AOS simulation to help the algorithm development)   # Update the test cases and [versionHistory.rst|https://github.com/lsst-ts/ts_MTAOS/blob/master/doc/versionHistory.rst] to reflect the change."
Answer: 42282.0