pygwinc issueshttps://git.ligo.org/gwinc/pygwinc/-/issues2021-09-02T23:23:39Zhttps://git.ligo.org/gwinc/pygwinc/-/issues/101how to setup matlab gwinc path2021-09-02T23:23:39ZRana Adhikarihow to setup matlab gwinc pathHaving trouble getting my old pygwinc code to find the correct matlab gwinc codes when load a coating config file.
How about adding a readme to the repo describing how to set that up?Having trouble getting my old pygwinc code to find the correct matlab gwinc codes when load a coating config file.
How about adding a readme to the repo describing how to set that up?https://git.ligo.org/gwinc/pygwinc/-/issues/90Documentation for yaml files2021-01-14T22:00:14ZKevin KunsDocumentation for yaml filesRelated to #88, we should add documentation for the yaml files instead of relying on the canonical IFOs as examples. There are options in the noise functions that don't have examples in these files or where the conventions and defaults a...Related to #88, we should add documentation for the yaml files instead of relying on the canonical IFOs as examples. There are options in the noise functions that don't have examples in these files or where the conventions and defaults are not obvious (for example the complicated behavior of [`getJointParams`](https://git.ligo.org/gwinc/pygwinc/-/blob/master/gwinc/suspension.py#L69) for specifying the suspensions or [`platform_motion`](https://git.ligo.org/gwinc/pygwinc/-/blob/master/gwinc/noise/seismic.py#L33) for specifying platform motion), and addressing #63 will introduce more.https://git.ligo.org/gwinc/pygwinc/-/issues/55auto docs: plots, sphinx, tags2020-04-02T00:51:34ZRana Adhikariauto docs: plots, sphinx, tagsI saw that their is some sporadic auto doxxing stuff that @lee-mcculler has put into some pygwinc areas.
A couple of thoughts on what would be nice:
1. copy the functionality of IDfig.m from matgwinc so that each plot has a tiny doc st...I saw that their is some sporadic auto doxxing stuff that @lee-mcculler has put into some pygwinc areas.
A couple of thoughts on what would be nice:
1. copy the functionality of IDfig.m from matgwinc so that each plot has a tiny doc string subtley stuck on the side that indicates which version of gwinc/magic was used, as well as what version of ifo.yaml, so that its easy to look up the params through GIT.
1. REAMDE files or web pages auto-gen by CI. Explain the physics of the noise sources, recent changes, drawings of the IFO config, etc.
1. When we make the multi page PDFs that havve the main noise + sub-buds, we could have some params data and explanastory tex in the last page.
+ other ideas people