- 19 Mar, 2016 2 commits
-
-
thomas.forbriger authored
The filter GaussianNoise is provided in tidofi through keyword noi. It adds white Gaussian Noise of a given rms amplitude (specified through filter parameter) to each time series. The filter is implemented in libtsxx. tidofi is additionally linked against libgsl to provide random number generator.
-
thomas.forbriger authored
-
- 08 Mar, 2016 1 commit
-
-
thomas.forbriger authored
-
- 04 Mar, 2016 4 commits
-
-
thomas.forbriger authored
-
thomas.forbriger authored
-
thomas.forbriger authored
Contents still referred to trac/SVN repository TFSoftware
-
thomas.forbriger authored
-
- 25 Feb, 2016 3 commits
-
-
thomas.forbriger authored
-
thomas.forbriger authored
Fix some sentences and expressions in the online description. These were not wrong previously but could be expressed in a more appropriate or consistent way.
-
thomas.forbriger authored
The offset dependent scaling factor was wrong incorrectly specified in the online documentation. Thanks to Florian for pointing this out.
-
- 08 Feb, 2016 8 commits
-
-
thomas.forbriger authored
-
thomas.forbriger authored
Merge branch 'issue7_refract' Advance refract version number to 4.14 This merge commit solves issues when scaling traces with an offset-dependent scaling factor. The modifications are prepared on branch issue7_refract. The issue observed with the previous version of refract was: Refract offers a power-law amplitude scaling. This must fail in cases where one of the traces is located at zero offset. In such cases the entire plot fails, which can confuse users not aware of this side-effect. This problem actually was caused by three problems in the code: 1 When using the zero offset (least offset) trace as a reference for offset dependent scaling (as is the default), a division by zero happens in subroutine mpcfactors. 2 Zero offset traces may come with an mpc-scaling factor equal to zero. This means, the trace should be down-scaled to a straight line in any case. The current concept of trace scaling does this by leaving the sample values of the trace as they are, by using a viewport for the trace according to current clipping (derived in function settracevp) and by setting the world coordinates for the trace's viewport appropriately (i.e. to infinity). In the latter step there happens the nasty division by zero (division by mpc factor). This problem is present, even if the zero offset trace is not used as a reference. 3 For a negative exponent the mpc factor of the zero offset trace would become infinite even for a finite reference value. These problems are addressed in the following way be this merge commit: 1 Problem is solved by referring amplitude scaling factors to the average scaled amplitude in a given offset range in scaling mode 2 and 3 (as was provided only in mode 3 so far), which now is the default way, the scaling reference is defined. 2 Problem is solved by setting an upper limit to the world coordinate range (in counts) in the trace's viewport, such that the trace is displayed as a straight line without causing numerical overflow. This is achieved by applying a lower limit ti mpc factors in subroutine refract_settracevp 3 Problem is solved by enforcing non-negative exponent value.
-
thomas.forbriger authored
By introducing an upper limit for the world coordinate range (in counts) in the display rectangle (viewport) of the trace, the program now is reobust in cases where zero-offset traces shall be displayed with offset dependend amplitude scaling. This is the final commit to resolve issue7.
-
thomas.forbriger authored
-
thomas.forbriger authored
-
thomas.forbriger authored
-
thomas.forbriger authored
Explain the different rectangle definitions used with in settracevp.
-
thomas.forbriger authored
sub/refract_settracevpold.f was kept for historical reasons to provide a reference to an obsolete way to set the trace view port. This file is from pre-CVS times. Source code history now is recorded in the repository. The file is obsolete.
-
- 01 Feb, 2016 1 commit
-
-
thomas.forbriger authored
-
- 07 Jan, 2016 1 commit
-
-
thomas.forbriger authored
-
- 08 Dec, 2015 1 commit
-
-
thomas.forbriger authored
- With the previous commits the average scaled amplitude in a given offset range is made the standard reference for amplitude scaling in modes 2 and 3. - This commit makes sure that the scaling exponent will never become negative. A negative scaling exponent would result in a singularity of scaled amplitudes at zero offset. Since amplitudes always are expected to decay with offset, negative exponents are not required for amplitude scaling.
-
- 07 Dec, 2015 17 commits
-
-
thomas.forbriger authored
-
thomas.forbriger authored
-
thomas.forbriger authored
-
thomas.forbriger authored
-
thomas.forbriger authored
-
thomas.forbriger authored
- discard obsolete variables - rename maxamp to refamp - add version comment
-
thomas.forbriger authored
This version compiles.
-
thomas.forbriger authored
Let subroutine mpcfactors select scaling factors relative of average scaled amplitude in defined offset range for scaling mode 2 and 3, both. This version does not yet compile.
-
thomas.forbriger authored
Provide new function to calculate average scaled amplitude to algorithm in subroutine mpcfactors. This version does not yet compile.
-
thomas.forbriger authored
-
thomas.forbriger authored
This version does not compile.
-
thomas.forbriger authored
This version does not compile
-
thomas.forbriger authored
Provide subroutine to set suitable offset range to determine reference amplitude for scaling, if not set by the user on the command line. This version does not compile.
-
thomas.forbriger authored
Provide new option - still must be implemented. This version does not compile.
-
thomas.forbriger authored
-
thomas.forbriger authored
-
thomas.forbriger authored
CVS ID keyword strings were remove with commit 2e81e847 on 2015-11-23. Some secondary string variables were missed then. Remove them now.
-
- 28 Nov, 2015 1 commit
-
-
thomas.forbriger authored
-
- 26 Nov, 2015 1 commit
-
-
thomas.forbriger authored
stuploxx uses libdatrwxx and therefor is able to handle a lot more formats than just SFF. In fact, the use of SFF has become insignificant, meanwhile.
-