156
edits
User:Josiah425:TISEAN Package: Difference between revisions
Jump to navigation
Jump to search
m
→General division
| (One intermediate revision by the same user not shown) | |||
| Line 19: | Line 19: | ||
* Linkable to FORTRAN (project, addnoise, lazy) | * Linkable to FORTRAN (project, addnoise, lazy) | ||
* Linkable to c (ghkss) | * Linkable to c (ghkss) | ||
I have already started working on this stage. My progress can be viewed at [https://bitbucket.org/josiah425/tisean | I have already started working on this stage. My progress can be viewed at [https://bitbucket.org/josiah425/tisean https://bitbucket.org/josiah425/tisean]. So far I have implemented addnoise, project and re-implemented henon as an mfile. As most work on this topic has been completed I estimate that finishing it up will take around 2 days -- throughout my outline I estimate about 1 day per program (that includes documentation and testing). | ||
==== Phase space representation ==== | ==== Phase space representation ==== | ||
This is the next topic that needs to be implemented. This is because it contains programs (especially 'delay') that are used to visualize data. Whenever an example is given in the package the resulting data is routed through 'delay' before it is plotted. Apart from delay it also contains other functions that can divided into the following categories: | This is the next topic that needs to be implemented. This is because it contains programs (especially 'delay') that are used to visualize data. Whenever an example is given in the package the resulting data is routed through 'delay' before it is plotted. Apart from delay it also contains other functions that can divided into the following categories: | ||
* Linkable to c (delay, corr, mutual, false_nearest, pca) | * Linkable to c (delay, corr, mutual, false_nearest, pca) | ||
There are two more programs in this section of the article they are: 'autocorr' and 'pc', both implemented in FORTRAN. There is no need to port them as according to the documentation ([http://www.mpipks-dresden.mpg.de/~tisean/Tisean_3.0.1/docs/contents.html | There are two more programs in this section of the article they are: 'autocorr' and 'pc', both implemented in FORTRAN. There is no need to port them as according to the documentation ([http://www.mpipks-dresden.mpg.de/~tisean/Tisean_3.0.1/docs/contents.html here]) they are redundant with other functions. Further more, it is likely 'corr' does not need to be implemented, because 'xcorr' in signal package seems to have similar functionality. This has not been confirmed yet, once that occurs, a definite answer can be given. | ||
Assuming around a day for each function (with testing and documenting the usage) I assume this stage will take a little under a week. | Assuming around a day for each function (with testing and documenting the usage) I assume this stage will take a little under a week. | ||
==== Nonlinear prediction ==== | ==== Nonlinear prediction ==== | ||
| Line 39: | Line 39: | ||
* Linkable to FORTRAN (c2, c2t, c2d, c2g, c1) | * Linkable to FORTRAN (c2, c2t, c2d, c2g, c1) | ||
* Linkable to C (d2, boxcount) | * Linkable to C (d2, boxcount) | ||
This part of the article also mentions 'c2naive' which is implemented in FORTRAN, but it is also described as redundant by the documentation ([http://www.mpipks-dresden.mpg.de/~tisean/Tisean_3.0.1/docs/contents.html | This part of the article also mentions 'c2naive' which is implemented in FORTRAN, but it is also described as redundant by the documentation ([http://www.mpipks-dresden.mpg.de/~tisean/Tisean_3.0.1/docs/contents.html here]) | ||
This stage should take little over a week. I expect this stage and the previous one to take about two weeks. | This stage should take little over a week. I expect this stage and the previous one to take about two weeks. | ||
==== Testing for nonlinearity ==== | ==== Testing for nonlinearity ==== | ||