ufechner7 / kiteutils.jl Goto Github PK

• use resize! before saving if less than the max number of steps where recorded
• do nothing when trying to log more than the reserved number of elements
• implement function length(logger::Logger)

Add the following fields to systems.yaml

    depower:   25.0        # initial depower settings    [%]

solver:
    abs_tol: 0.0006        # absolute tolerance of the DAE solver [m, m/s]
    rel_tol: 0.001         # relative tolerance of the DAE solver [-]
    max_iter:  200         # max number of iterations of the steady-state-solver
    
kite:
    physical_mode: "KPS4"
    version: 1

Release the first stable version.

The function copy_settings should copy the settings files and make them writable.

Add an arc cos function that allows arguments slightly above one and below minus one to avoid exceptions in case of rounding errors.

Use SVectors instead of Vectors...

It should be allowed to omit the section kps4_3l if it is not needed.

This function should re-read the file settings.yaml

@JuliaRegistrator register()

With the package StructTypes.jl it is possible to create a settings struct from a dictionary automatically without writing code for each field. This greatly simplifies the function se() and also makes it easier to add new fields in the future.

All functions that expect a file name should:

• allow the use of a fully qualified file name
• use the default path if no path is given

@JuliaRegistrator register()

Can be enabled in CI.yml

For testing of KiteViewers.jl add a function that provides a state including a 4 point kite.

• Add to settings.yaml
• add to Settings struct
• add code for filling the struct from the yaml file

@JuliaRegistrator register()

• adapt function save_log
• adapt function read_log
• save_log should create a filename of the following form: sim_log_6s_4p.arrow
• read_log should retrieve the correct number of points from the filename
• add function is_4p(filename)
• update documentation

Add the following fields:

• steering
• vel_kite (vector)
• heading
• course

Alternatively provide functions that calculate heading and course from a SysState object.

• create a test project
• use of settings
• using the type SysState
• using log.syslog
• using the type SysLog

• improve save_log()
• improve load_log()
• add function kitemodel(log)

@JuliaRegistrator register()

This issue is used to trigger TagBot; feel free to unsubscribe.

If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.

If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Add functions to calculate heading, course etc...

• add description of free variables
• fix the example of loading a log file

Make it possible to log 16 variables per time step.

If set_data_path() is called, then the default settings from the folder data of the package KiteUtils shall be loaded when calling se() instead of the customized settings from the data folder of the current project.
To undo this call, call set_data_path("data").

Currently SysState has the fields X, Y and Z, but no property that provides a vector of positions. This shall be added.

When you add this package to your own project and then run
]test it will fail due to missing write permissions to the data folder.

Use a scratch space for test data to avoid this issue.