ctn_noisebudget issueshttps://git.ligo.org/cit-ctnlab/ctn_noisebudget/-/issues2019-09-26T23:07:54Zhttps://git.ligo.org/cit-ctnlab/ctn_noisebudget/-/issues/8Uncertainty latest version has a problem with Coating Thermo-Optic Noise calc...2019-09-26T23:07:54ZAnchal GuptaUncertainty latest version has a problem with Coating Thermo-Optic Noise calculationThis was known in the older noise budget as well as there was a distinctive direction at the top to use uncertainties package 2.4.8.1.
This version of the package calculates the standard deviation of the quantities on the run and hence m...This was known in the older noise budget as well as there was a distinctive direction at the top to use uncertainties package 2.4.8.1.
This version of the package calculates the standard deviation of the quantities on the run and hence make complex calculations significantly longer. With the latest addition of uncertainty calculation in the Coating Brownian noise, this has reached roughly 1.5 hrs of run time for the code. But it at least works.
If we run the code with uncertainties package 3.1.2 which is the latest one, the code runs lightning fast as this package leaves the calculation of standard deviation on a need basis, so essentially when it is tried to be printed, saved or plotted. However, this makes it a bad choice when a variable's standard deviation is calculated repeatedly because it was referenced by many other variables. This is happening presently with the coating thermo-optic noise. Hence, we can't run this code with the latest version of uncertainties package.
This needs to be resolved as we can't use two different versions of the package for different parts of the code. Options:
1) Make coating brownian noise calculation more efficient so that it runs faster with uncertainties package 2.4.8.1. This would be little bad though as we will be relying on an outdated package which has other problems and fewer features.
2) Make the thermo-optic noise calculation such that the traceback to calculate standard deviation in final result does not take too long. I have opened an issue in [uncertainties package repo](https://github.com/lebigot/uncertainties/issues/105) to see what the developers think about this issue.Anchal GuptaAnchal Guptahttps://git.ligo.org/cit-ctnlab/ctn_noisebudget/-/issues/7Refactor noiseBudget.ipynb as a class2019-08-29T01:52:43ZAndrew WadeRefactor noiseBudget.ipynb as a classnoiseBudget.ipynb is one big long script; one that can be executed in order or out of order. Given the modularity of the different noise sources it would make sense to reformulate it as a class with a decent __init__ function. Something...noiseBudget.ipynb is one big long script; one that can be executed in order or out of order. Given the modularity of the different noise sources it would make sense to reformulate it as a class with a decent __init__ function. Something similar to the implementation of pyliso.
This would help neaten up the implementation and make clear what variables were global and what should be kept local to individual noise functions. Right now it is hard to implement competing models of thermal noise for fear of contaminating the variable name space with conflicting namings. That's just bad python coding.
It would also help with version control as hot fixes on master, and also branching and merging, work much better on plain text files compared to jupyter notebook markup. The codebase will be more maintainable in the longer term
We should evolve noiseBudget.ipynb to have an import command for the class and mainly be markup with background and theory, configuration for specific coatings and pretty plots.https://git.ligo.org/cit-ctnlab/ctn_noisebudget/-/issues/6Repo need trimming2019-08-29T02:37:50ZAndrew WadeRepo need trimmingThis repo has become bloated with auxiliary materials. We need to strip it back to just the AlGaAs CTN budget and flatten commit history over the time when we were committing daily noise budget material, pdfs plots and other non-essenti...This repo has become bloated with auxiliary materials. We need to strip it back to just the AlGaAs CTN budget and flatten commit history over the time when we were committing daily noise budget material, pdfs plots and other non-essential data files.
Filing as an issue so we can tick it off at some stage.https://git.ligo.org/cit-ctnlab/ctn_noisebudget/-/issues/5FSS_all.fil throwing error with eomHV added2019-08-29T01:53:04ZAndrew WadeFSS_all.fil throwing error with eomHV addedThrowing a unknown error. When run from pyliso unknown error means it has no output when testing from nodes eomHVn1 and eomHVn11.Throwing a unknown error. When run from pyliso unknown error means it has no output when testing from nodes eomHVn1 and eomHVn11.Andrew WadeAndrew Wadehttps://git.ligo.org/cit-ctnlab/ctn_noisebudget/-/issues/4Construct a testing script for noise budget2017-10-31T16:54:02ZAndrew WadeConstruct a testing script for noise budgetNeed to configure workbook and its output to sense when it is being run as a script by a python interpreter and run quality/run checks to generate a noise budget.
A nice add on would be to have it generate a live updated noise budget pl...Need to configure workbook and its output to sense when it is being run as a script by a python interpreter and run quality/run checks to generate a noise budget.
A nice add on would be to have it generate a live updated noise budget plot uploaded to gitlab wiki, nodus or ldas.https://git.ligo.org/cit-ctnlab/ctn_noisebudget/-/issues/3Shift CTN_noisebudget and ctn_labdata to CIT_CTN group ownership2017-10-18T18:40:36ZAndrew WadeShift CTN_noisebudget and ctn_labdata to CIT_CTN group ownershipDo it.Do it.Andrew WadeAndrew Wadehttps://git.ligo.org/cit-ctnlab/ctn_noisebudget/-/issues/2Shift all historic data to git2019-08-29T01:53:35ZAndrew WadeShift all historic data to gitNeed to move all historic data from cloud sync folders to git.Need to move all historic data from cloud sync folders to git.Migrate data filesAndrew WadeAndrew Wadehttps://git.ligo.org/cit-ctnlab/ctn_noisebudget/-/issues/1Data needs to be moved to data repo2019-08-29T01:53:50ZAndrew WadeData needs to be moved to data repoNot sure what you've moved over yet. We should keep all the data folders in the separate data repo, unless they need to be called from these models and scripts.Not sure what you've moved over yet. We should keep all the data folders in the separate data repo, unless they need to be called from these models and scripts.Migrate data filesCraig Cahillanecraig.cahillane@ligo.orgCraig Cahillanecraig.cahillane@ligo.org2017-08-27