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: "Traffic soak lab, long run of major release, never stop running (and could practice upgrade/swap in fixes as necessary here)  "
Answer: 302359.0

User story: "Long test runs over multiple days  "
Answer: 57999.0

User story: "Script development for long runs and uploading the tests in repo"
Answer: 50518.0

User story: "Investigation on the tools that can be used for Load testing"
Answer: 302370.0

User story: "Follow SDK spec and refer to nodeJS SDK implementation."
Answer: 35022.0

User story: "The test automation tools should be modified such that we can change the SDK used as a parameter and without code changes. This will allow us to know if there are any issues more quickly between the different SDKs and find those holes more quickly.     This can also come in handy when working with customers to know which SDKs they are using and possible issues that may be present as a result.  "
Answer: 978858.0

User story: "When a customer has backups of the peer ledger (no need to do anything with couchdb database), can that backup database replace the original and continue with execution as needed? Stop a peer some time after a backup is made, copy the old ledger backup in to replace the newer one, and restart the peer.    Expected result: There should be no problems. Execution should continue as if it were the original ledger. Peer will resume, and catchup all blocks.    This can be added as a behave test for automation."
Answer: 1003145.0

User story: All tests used for testing hyperledger/fabric should be submitted to github.     Code should eventually be in hyperledger/fabric repository in the bddtests directory. There should also be a directory "extended_regression" in the bddtests directory.
Answer: 37315.0

User story: "We can use ansible for monitoring the peers within a network. This includes CPU, memory, disk space, etc..."
Answer: 302472.0

User story: "We can use ansible for deployment of peers given certain environment and docker variables that are used and selected at execution time. The deployment should be flexible enough such that changes to the ansible script should be minimal when certain features may or may not be required per execution."
Answer: 127904.0

User story: "This change:  1) Helps connect between the existing fabric message verification API to the gossip implementation by using the same signature methods as the crypto/crypto.go Peer interface 2) Adds a PKI_id to the discovery infrasturcture and to the communication layer in order for peers to assert:   * Single connection to each peer   *  Identity of connecting peer    Commit:  ff9c4f30e68eead76005116fb77badf22e7e6106  Gerrit:  https://gerrit.hyperledger.org/r/#/c/1343/"
Answer: 7204.0

User story: "The orderer must be able to parse the content of a configuration transaction, whether this means pulling in the system chaincode execution environment from the peer, or more manually reading raw postimage data from the transaction itself.  The complexity vs reuse will need to be carefully weighed for this story."
Answer: 80307.0