Skip to content

Register package #9

Description

@ufechner7

Activity

  1. ufechner7 commented on Jan 3, 2022

    @ufechner7
    MemberAuthor
  2. JuliaRegistrator commented on Jan 3, 2022

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/51591

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.1.0 -m "<description of version>" 309e15d0eef35c793e6fe737c6e753072838e17b
    git push origin v0.1.0
    
  3. ufechner7 commented on Jan 3, 2022

    @ufechner7
    MemberAuthor
  4. JuliaRegistrator commented on Jan 3, 2022

    @JuliaRegistrator

    Registration pull request updated: JuliaRegistries/General/51591

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.1.0 -m "<description of version>" 37ee55280b24ed18cc34a8cc304b54653dbdfee4
    git push origin v0.1.0
    
  5. ufechner7 commented on Mar 13, 2022

    @ufechner7
    MemberAuthor
  6. JuliaRegistrator commented on Mar 13, 2022

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/56517

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.2.0 -m "<description of version>" 722a791c35205619b2cb574c1d60ca187a677678
    git push origin v0.2.0
    
  7. ufechner7 commented on Apr 17, 2022

    @ufechner7
    MemberAuthor
  8. JuliaRegistrator commented on Apr 17, 2022

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/58644

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.3.0 -m "<description of version>" e5420062c70da5c8d8e6c181bf12aa80f476ddcf
    git push origin v0.3.0
    
  9. ufechner7 commented on Apr 17, 2022

    @ufechner7
    MemberAuthor
  10. JuliaRegistrator commented on Apr 17, 2022

    @JuliaRegistrator

    Registration pull request updated: JuliaRegistries/General/58644

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.3.0 -m "<description of version>" 33144e8ff20458071f99e5271a6da3e487e22631
    git push origin v0.3.0
    
  11. ufechner7 commented on Apr 18, 2022

    @ufechner7
    MemberAuthor
  12. JuliaRegistrator commented on Apr 18, 2022

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/58689

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.3.1 -m "<description of version>" b1e80d381ca80588bc26e62050bdccf137593659
    git push origin v0.3.1
    
  13. ufechner7 commented on Apr 20, 2022

    @ufechner7
    MemberAuthor
  14. JuliaRegistrator commented on Apr 20, 2022

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/58810

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.3.2 -m "<description of version>" 497b65525611fe36fe0943640aee13b4af243729
    git push origin v0.3.2
    
  15. ufechner7 commented on May 2, 2022

    @ufechner7
    MemberAuthor
  16. 166 remaining items

  17. JuliaRegistrator commented on May 8, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/154969

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.11.12 -m "<description of version>" 654b60cbb74f6a2b25fbd5dddb9d9425c473c6fd
    git push origin v0.11.12
    
  18. ufechner7 commented on May 14, 2026

    @ufechner7
    MemberAuthor

    @JuliaRegistrator register

    Release notes:

    KiteModels v0.11.13 2026-05-14

    Added

    • Use PythonCall (Use PythonCall #286): updated to ControlPlots 0.3, which uses PythonCall instead of PyCall
    • Documented turbulence in the documentation (docs/src/projects.md)
    • Forward script arguments to Julia in bin/run_julia
    • Added CondaPkg directory to .gitignore
    • Added missing imports in examples/rotations.jl
    • Updated bin/reuse_lint script
    • Added Julia version selection dialog to bin/update_default_manifest
    • Run tests also on Julia 1.11 in bin/install
    • Suppress verbose CondaPkg logs in bin/setup_env

    Changed

    • Use -t auto in bin/run_julia to allow multithreading in the REPL
    • Improved examples_3d/parking_wind_dir.jl example
    • Improved plots in examples_3d/parking_wind_dir.jl and examples_3d/plot_turbulence.jl
    • Updated documentation build (docs/make.jl)
    • Cleaned up removed initial_reel_out_4p example files
    • Improved comments throughout the codebase
    • Improved messages in bin/install

    Fixed

    • Fixed Windows compatibility in bin/setup_env
    • Fixed bug in examples/rotations.jl
    • Fixed Pkg.test() call for Julia 1.11 in bin/install
  19. JuliaRegistrator commented on May 14, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/155472

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.11.13 -m "<description of version>" 4432376c192cbe16baf26d9a7c7bcdee8dd52ed4
    git push origin v0.11.13
    
  20. ufechner7 commented on Jun 20, 2026

    @ufechner7
    MemberAuthor

    @JuliaRegistrator register

    Release notes:

    Added

    • Added function reel_out_speed to KiteModels.jl, KPS3.jl, and KPS4.jl
    • Added output/ directory to .gitignore

    Changed

    • Switched from ControlPlots to MakieControlPlots across all examples, tests, docs, and scripts (Switch from ControlPlots to MakieControlPlots #295)
    • Removed bin/install_controlplots
    • Added a 25 ms delay to each plot2d call to match the previous ControlPlots behavior
    • Cleaned up bin/install: no special handling for ControlPlots anymore
    • examples/reel_out_4p_torque_control.jl now uses reel_out_speed and interface functions, and plots heading and wind at kite
    • Updated PR template: replaced "Lint workflow is passing" with "JETLS is not reporting any warnings"; updated docs check to reference scripts/build_docu.jl
    • Updated default manifests (Manifest-v1.11.toml.default, Manifest-v1.12.toml.default)
    • Removed obsolete mwes files (mwe_03 – mwe_14, mwe_20, mwe_21)
    • Removed TestEnv references from remaining mwes scripts
    • Bumped MakieControlPlots to version 0.1.4 to fix a bug with plot2d and missing parameter support

    Fixed

    • Fixed plotting issue in examples after migration to MakieControlPlots
    • Fixed jetls warnings: sorted using imports alphabetically in auto_parking_4p.jl, parking_wind_dir.jl, and plot_turbulence.jl
    • Fixed jetls warning: removed unused y_label assignment in reel_out_1p.jl
    • Fixed jetls warning: removed redundant last_heading initialization in steering_test_1p.jl and steering_test_4p.jl
  21. JuliaRegistrator commented on Jun 20, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/158564

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.11.14 -m "<description of version>" 6111ca844ccd65e98f37f7d55e9e9aee1a25b4a8
    git push origin v0.11.14
    
  22. ufechner7 commented on Jul 24, 2026

    @ufechner7
    MemberAuthor

    @JuliaRegistrator register

    Release notes:

    Added

    • Added CLAUDE.md with guidance for Claude Code when working in this repository
    • Added bin/release script for creating a new release

    Changed

    • KPS4.wm field type widened from Union{AsyncMachine, TorqueControlledMachine} to WinchModels.AbstractWinchModel, allowing other WinchModels subtypes
    • bin/create_sys_image now prints a success message when the system image is created
    • bin/run_julia no longer probes for and loads Kaimon
  23. JuliaRegistrator commented on Jul 24, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/162258

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.11.15 -m "<description of version>" 183ee0b5c1f65424da2d2ef0b8d6278c85e86adf
    git push origin v0.11.15
    
  24. ufechner7 commented on Aug 10, 2026

    @ufechner7
    MemberAuthor

    @JuliaRegistrator register

    Release notes:

    Added

    • next_step! and set_v_wind_ground! accept the keyword argument interpolate (default false,
      the previous behaviour), which is passed on to calc_turbulent_wind: the turbulence is then
      interpolated trilinearly between the grid points of the wind field instead of being read at the
      nearest one, so the kite no longer flies through steps in the wind. Without turbulence it has no
      effect. examples_3d/parking_wind_dir.jl switches it on via its INTERPOLATE parameter.
    • test/test-update-sys-state.jl covers update_sys_state! for both KPS3 and KPS4: every field
      against the getter it comes from, the zoom scaling, nothing set values logging as NaN, the
      turn rate around the body z-axis, and the shortest-angle difference that keeps heading_rate and
      azimuth_rate free of spikes at the wrap boundary.

    Changed

    • calc_turbulent_wind no longer duplicates the wind field lookup: it forwards to
      AtmosphericModels.calc_turbulent_wind, which the two fixes below had brought it in line with
      anyway. The results are bit-identical, the signature (am, pos, upwind_dir, t) is unchanged, and
      the new keyword argument interpolate is passed through, so the turbulence can now be
      interpolated between grid points instead of being read at the nearest one.
    • set_v_wind_ground! had a second copy of the mean wind profile for the case
      use_turbulence == 0. It now takes both the mean and the turbulent wind from
      calc_turbulent_wind, so the height profile has one implementation. The turbulent branch
      used to evaluate the wind field at pos_kite(s)[3] and ignore the height argument; it now
      uses height, which every caller in this package passes as calc_height(s) anyway.

    Fixed

    • calc_turbulent_wind scaled the sampled turbulence with rel_turbo(am) only. As of
      AtmosphericModels 0.3.8 the stored wind field has the reference intensity instead of being
      pre-scaled by use_turbulence, so the factor is now applied here; without it, every simulation
      would have flown at full Cabauw turbulence regardless of the setting. AtmosphericModels compat
      raised to 0.3.8 accordingly — with an older version the field is pre-scaled and the factor
      would be applied twice.
    • calc_turbulent_wind took the rel_turbs correction for set.v_wind (rel_turbo(am)) while
      the wind field itself may have been loaded for a different ground wind speed. It now reads
      am.wf.v_wind_gnd, the speed the loaded field was generated for, so the two can no longer
      disagree.
  25. JuliaRegistrator commented on Aug 10, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/164036

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.11.16 -m "<description of version>" 1ccaafdb37a6a7eb91a51cb82fb94acc56aacc32
    git push origin v0.11.16
    
  26. ufechner7 commented on Oct 9, 2026

    @ufechner7
    MemberAuthor

    @JuliaRegistrator register

    Release notes:

    Added

    • next_step! accepts the keyword argument v_wind_vert (default 0.0, fully backward compatible)
      for injecting a constant vertical wind component (updraft/downdraft) at the kite. It is stored in
      the model struct and added to s.v_wind[3] by set_v_wind_ground! on top of whatever the wind
      model (laminar or turbulent) already produces, so turbulent vertical wind is not overwritten.
      Positive is up. Only s.v_wind is affected — s.v_wind_gnd and s.v_wind_tether stay unchanged,
      so upwind_dir and tether drag are unaffected; a future phase 2 could extend the tether. Since
      v_wind_kite(s) returns s.v_wind, the component shows up in the logged v_wind_kite state
      automatically.
    • Support for Julia 1.13: julia compat entry extended to 1.11, 1.12, 1.13 (also in the docs,
      examples and examples_3d projects), new default manifest Manifest-v1.13.toml.default (with
      some packages downgraded to reduce the size of the system image), and bin/install offers
      Julia 1.13 as a third choice (the default if it is already the active juliaup channel).

    Changed

    • Parameters compat widened to 0.12, 0.13.
    • bin/install and bin/create_sys_image pick the default manifest generically as
      Manifest-v<julia_major>.toml.default and fail if it is missing; bin/create_sys_image no longer
      deletes the obsolete data/model_*.bin files, and bin/create_sys_image2 also backs up
      Manifest-v1.13.toml when updating.
    • README and documentation: links to WinchModels, KitePodModels and AtmosphericModels point to
      the OpenSourceAWE organisation, the package diagram is taken from KiteUtils.jl, Julia 1.12 is
      the recommended version, and the reference to the meta-package KiteSimulators was dropped.

    Removed

    • bin/setup_env (the LD_PRELOAD/LD_LIBRARY_PATH workaround) and bin/jetls_with_env, which
      depended on it. bin/install, bin/run_julia, bin/create_sys_image and bin/create_sys_image2
      no longer source it, and the retry without these overrides is gone. copy_bin() no longer copies
      setup_env.
    • Obsolete data/model*.bin / data/prob*.bin entries from .gitignore.
  27. JuliaRegistrator commented on Oct 9, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/171176

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.11.17 -m "<description of version>" 82cceaf1ed24b7af8c51e0e912b3829dfc91e49b
    git push origin v0.11.17
    
  28. ufechner7 commented on Oct 10, 2026

    @ufechner7
    MemberAuthor

    @JuliaRegistrator register

    Release notes:

    Changed

    • The system of equations of find_steady_state! (KPS4) is now square and well-posed. Before, one
      unknown had no effect, one equation was missing (its entry stayed 0), and the x equation of the
      point p8 was used twice, so the elevation of the kite could drift from set.elevation by several
      degrees, depending on rounding. Now the elevation of the kite (pos_kite, so that
      calc_elevation(s) returns set.elevation) is prescribed instead of the z balance of the kite
      points C and D (the kite can only be fully balanced at its natural elevation), C and D enter as
      symmetric (x) and antisymmetric (y) combination, and the unused unknown is fixed to zero. The
      initial state of the simulation changes slightly.

    Fixed

    • find_steady_state! (KPS4) is more robust: if the first nlsolve attempt fails or returns
      a result with a large residual, it is retried without autoscaling and then by continuation
      (solving for an easier stiffness_factor/delta first and stepping towards the requested values).
      Before, convergence depended on tiny floating-point differences, so e.g. the hydra20_426
      project of KiteControllers.jl failed to initialise on Julia 1.13 while it worked on Julia 1.12.
    • a residual entry that is not used as equation could keep the value 1e6 after an infeasible
      solver step; it is now reset on every evaluation
    • the warning "Warning in test_initial_condition!" for infeasible solver steps is now a debug message
    • find_steady_state! now also warns if the solver stopped because the steps became small while the
      residual norm is still above 1e-3; before, such a result was accepted silently. The warning now
      includes the residual norm.

    Added

    • test test/test-steady-state-robustness.jl for cases where a single solver attempt does not converge
  29. JuliaRegistrator commented on Oct 10, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/171223

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.11.18 -m "<description of version>" c1e06b37c1665a7ca120a167d01428baefe0188f
    git push origin v0.11.18
    
  30. ufechner7 commented on Oct 10, 2026

    @ufechner7
    MemberAuthor

    @JuliaRegistrator register

    Release notes:

    Fixed

    • The state of the winch (brake on/off, rate limited set speed) is now updated once per time step
      in next_step! (and reset in init! to the initial set speed set.v_reel_out and the brake
      state after construction, so that repeated calls of init! give the same result) instead of on
      every call of the residual function. Before, it depended on the number of residual evaluations
      of the DAE solver, so tiny numerical differences (e.g. between Julia versions) could switch the
      brake at a different moment. With a winch v_min of 0.15 m/s this made the reel-out speed of the
      hydra20 simulations of KiteControllers.jl run away on Julia 1.13. The simulation results change
      slightly.
    • find_steady_state! (KPS3) now finds a real equilibrium. Before, nlsolve usually stopped
      because its steps became tiny, with the accelerations of the tether particles still at about
      25 m/s², and on some machines it printed find_steady_state!: solver did not converge!. The
      unknowns are now the angles and relative stretches of the tether segments instead of the offsets
      of the particle positions, the solver starts from a slightly stretched tether (the spring force
      has a kink at zero stretch), and, as for KPS4, the elevation of the kite is prescribed instead of
      its vertical force balance, so calc_elevation(s) returns set.elevation. The tether particles
      and the horizontal force balance of the kite are now solved to ftol = 1e-6; a warning is only
      printed if this fails. The horizontal residuals are taken in the plane of the tether, so the
      result no longer depends on upwind_dir. The initial state changes: for example, with a 392 m
      tether the kite starts at 70° instead of 64.3°.

    Changed

    • requires WinchModels 0.3.12 (for update_winch_state! and calc_acceleration(...; update_state))
    • support Julia 1.12 and 1.13 only, as WinchModels 0.3.12 and KiteUtils do: julia compat
      "1.12, 1.13", Manifest-v1.11.toml.default is removed, bin/install,
      bin/update_default_manifest and bin/create_sys_image no longer offer Julia 1.11, CI tests
      Julia 1.12 instead of 1.11, and the docs no longer mention Julia 1.11
    • the default manifests for Julia 1.12 and 1.13 use WinchModels 0.3.12 and the latest versions of
      the other dependencies
  31. JuliaRegistrator commented on Oct 10, 2026

    @JuliaRegistrator

    Registration pull request created: JuliaRegistries/General/171275

    Tagging

    After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

    This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

    git tag -a v0.11.19 -m "<description of version>" 904a7dad18e79e6adaf1ce82b3f3057cafaed108
    git push origin v0.11.19
    
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions