Skip to content

Milestones

List view

  • No due date
    1/1 issues closed
  • Hey Hey, as told before I would like to incorporate my time evolution code written for my research in `HarmonicBalance.jl`. I opted to make a new package which plays nicely with `HarmonicBalance.jl`. This has the advantage that `HarmonicBalance.jl` becomes less bloated, as it is know. That is because we can move all time evolving related code (parameter sweep, slow-flow time evolution, etc.) to this new package such that the packages `FFTW, Peaks, DSP and OrdinaryDiffEq` can be removed. This will reduce the compilation time if one want just compute the steady-states of the slow and the extra feature are still there if one just loads an extra package `TimeEvolution.jl` were the remaining features reside. To achieve this result I had to make sure that the packages play nicely. So I split `HarmonicBalance.jl` in two: `HarmonicBalanceBase.jl` and `HarmonicBalance.jl`. `HarmonicBalanceBase.jl` contains al the the types and the code to create the slow-flow equations. `HarmonicBalance.jl` loads `HarmonicBalanceBase.jl` and add all functionality regarding computing steady states, plotting and etc. The end user will not notice anything changed. The new package will also load `HarmonicBalanceBase.jl` and add all time evolution stuff. Because they both load `HarmonicBalanceBase.jl`, the packages are complementary, and, hence, work very nice together. I know this is a big change, but I really take it is for the better. I already did everything and it works perfectly (the tests run). The repo's can be found here: * [HarmonicBalance.jl](https://github.com/oameye/HarmonicBalance.jl/tree/HarmonicBalance_cleaned): Better to move it as a branch under `NonlinearOscillations/HarmonicBalance` but do not have access * [HarmonicBalanceBase.jl](https://github.com/NonlinearOscillations/HarmonicBalanceBase.jl) * [TimeEvolution.jl](https://github.com/NonlinearOscillations/TimeEvolution.jl) (name up discussion; I like NonlinearOscillationDynamics; although long): This is integration is not finished but will be likely finished tomorrow.

    No due date
    3/3 issues closed