fixing bug where extraction radius was assumed to be the number trailing the...

fixing bug where extraction radius was assumed to be the number trailing the 'r' character in the file names; the true radius sits in the header of the data file

added 1 commit

• b9dadeb2 - redo previous fix to actually work

Compare with previous version

approved this merge request

Approved merger request, although it comes with another bug. The latter will be fixed in a following commit.

unapproved this merge request

closed

reopened

changed target branch from development to master

corrected the wrongly implemented fix

updated the merge request to merge into master, since development disappeared

added 1 commit

• d942a05e - removed unused filename variable

Compare with previous version

Please check: it seems to me the current cod eon master does not require this patch anymore.

I am sorry, but I can't see it anywhere ...

To me it seems like that the method wave.prop_read_from_file does not yet handle the special cases for parsing the detector radius for bam and core, see https://git.tpi.uni-jena.de/core/watpy/-/blob/master/watpy/wave/wave.py#L425 This patch adds the same checks as done in mwaves. Although one could also fuse them into wfile_parse_name...

Or am I missing something here?

added 7 commits

• d942a05e...41e41181 - 6 commits from branch master
• a4cbce8b - merged updates from master

Compare with previous version