2019 July release

[aewallin]

It is probably time for a new release (see #88) - sometime towards the end of July 2019.
This issue is to discuss what we want to include (or not) before the release.

@aewallin to-do list

• recall and document the release-process on github/pypi
• add real-time ADEV (etc.) functions that operate on a stream of samples.
• readthedocs build fixed (was not updated in 4 months or so..)

issues (to be) fixed:

• #88 pypi install broken for python3(?)
• #70 kw-args for Plot()
• #74 length of noise.Pink()
• #21 mtotdev() htotdev() are very slow
• #51 enabled cs-dataset test again. it is quite slow but maybe it's OK anyway.
• #82 mtie() consumes too much memory

General to-do list:

• #97 save dataset results to file
• decide on datetime functionality (#87) - leaving them out - add documentation on different datetime alternatives
• improve documentation (e.g. #55)

please add your ideas/comments/to-do-lists below - thanks.

[Deleted user]

Hi Anders, idea maybe: make the /frequency2phase()/ function capable of handling data with holes (represented by NaN). F. Le 03/07/2019 à 18:53, Anders Wallin a écrit :

…

It is probably time for a new release (see #88 <#88>) - sometime towards the end of July 2019. This issue is to discuss what we want to include (or not) before the release. @aewallin <https://github.com/aewallin> to-do list * recall and document the release-process on github/pypi * make lag-1 autocorrelation the default noise-ID algorithm and compute confidence intervals (#47 <#47>) from this * add real-time ADEV (etc.) functions that operate on a stream of samples. * maybe revisit #44 <#44> (again!) - can we get rid of the scipy dependence? General to-do list: * resolve any open issues, if possible * decide on datetime functionality (#87 <#87>) - I would lean towards leaving them out. * improve documentation (e.g. #55 <#55>) * improve test coverage on coveralls * add new python-versions (?) or OSs (?) for travis-testing. Travis should be able to test on Mac OSX and Win also now. Algorithms: * GCOV (Vernotte/Rubiola et al) could be interesting - for three-cornered-hat analysis * PVAR/PDEV (Danielsson et al, ping @sa0mad <https://github.com/sa0mad>) ? * relation between time-series, xDEV, phase-noise (dBc/Hz, dBrad/Hz), rms jitter please add your ideas/comments/to-do-lists below - thanks. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#89?email_source=notifications&email_token=AJUGMMXDSHP4HBBOEHUMEOTP5TKQ3A5CNFSM4H5HY2TKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G5F4UOA>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJUGMMVSQT5J6KTKUPVPQTTP5TKQ3ANCNFSM4H5HY2TA>.

[aewallin]

idea maybe: make the /frequency2phase()/ function capable of handling data with holes (represented by NaN).

Do you have a particular paper/reference in mind for different ways of handling this? It seems there are many ways: just ignoring gaps, filling them with a linear interpolation between existing datapoints, filling them with some noise model estimated from valid datapoints, etc.

[yxie-git]

I agree with @ffrank14. Maybe the input can be in two columns: MJD and data, and then the frequency2phase()/phase2frequency() function can detect gaps. Stable32 gives several ways to deal with these gaps: e.g. gaps are ignored in ADEV, while gaps are filled in MDEV. But I found an issue: when processing data with gaps, the ADEV results are worse (ADEV values are larger) in the case of firstly phase2freq conversion than direct calculation on phase data. That might be related to the gaps ignorance. If this issue can be improved, that would be nice.

[aewallin]

2019.07.rc1 is now tagged and uploaded to pypi:
https://pypi.org/project/AllanTools/2019.7rc1/

the instructions say to test with "pip install AllanTools==2019.7rc1"

If you could please test within one week and report any potential problems - thanks! (I'll try to release the final version August 3rd-4th)

[aewallin]

Things that we did not have time to fix for this release are now moved to #101

I plan to tag the 2019.07 release on about August 4th

[fmeynadier]

FWIW: installs smoothly on a win10 / python 3.6.6 environment I don't usually use for development.
However one of the tests fails: write_results in test_dataset.py.

 PermissionError: [Errno 13] Permission denied: 'C:\\Users\\FREDER~1.MEY\\AppData\\Local\\Temp\\tmpybjzk6hn'

The function itself works if you use it as intended, I think it is just an issue with Windows handling the temporary file creation in the test.

[aewallin]

seems that unix and win work a bit different, google finds this: https://stackoverflow.com/questions/23212435/permission-denied-to-write-to-my-temporary-file it should be possible to get travis to run the tests under windows (and mac osx) - that would catch things like this..

…

On Thu, Aug 1, 2019 at 5:51 PM fmeynadier ***@***.***> wrote: FWIW: installs smoothly on a win10 / python 3.6.6 environment I don't usually use for development. However one of the tests fails: write_results in test_dataset.py. PermissionError: [Errno 13] Permission denied: 'C:\\Users\\FREDER~1.MEY\\AppData\\Local\\Temp\\tmpybjzk6hn' The function itself works if you use it as intended, I think it is just an issue with Windows handling the temporary file creation in the test. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#89?email_source=notifications&email_token=AAG6BRJOWMCPZOGNAWZKPSLQCLZ5RA5CNFSM4H5HY2TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3K3GDY#issuecomment-517321487>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAG6BRMUCO222X575V6KG7DQCLZ5RANCNFSM4H5HY2TA> .

[aewallin]

#102 is now some (initial) steps towards getting travis to test on OSX and WIN also.

[aewallin]

@fmeynadier travis now catches the problem with tempfile on windows, see #103

[aewallin]

2019.07 now released, further discussion of new features at #101
closing this issue.