Register package

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Error while trying to register: "Pre-release version not allowed"

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/103042

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.1 -m "<description of version>" 1d6668c5a07285d3d280418da81c5c3da9252f1f
git push origin v0.0.1

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/103049

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.1 -m "<description of version>" 81957b903ed4dd3d506ffadb293eb5b82cdbad3d
git push origin v0.0.1

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/103490

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.1 -m "<description of version>" ccd15771726d63677c2cfb1fd06904b65b277d36
git push origin v0.0.1

[ufechner7]

@JuliaRegistrator register

Release notes:

Changed

• plotting should now also work when using this package with PackageCompiler

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/104262

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.0.2 -m "<description of version>" c4a2a373e43ffb1b9c6894b258166be3d52d311e
git push origin v0.0.2

[ufechner7]

@JuliaRegistrator register

Release notes:

Added

• new version of function plot() that allows to plot multiple time series in one plot

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/104267

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.0.3 -m "<description of version>" f9f2124a84cb08c519300afabdd41a706bf3f3b3
git push origin v0.0.3

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/104267

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.0.3 -m "<description of version>" f9f2124a84cb08c519300afabdd41a706bf3f3b3
git push origin v0.0.3

[ufechner7]

@JuliaRegistrator register

Release notes:

Changes

• rename plot to plotn (for multiple time series in one diagram)

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/104270

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.0.4 -m "<description of version>" dba48d0e422777b312618aff15b0cdc635b4ee67
git push origin v0.0.4

[ufechner7]

@JuliaRegistrator register

Release notes:

Breaking

• replace plotn() with plot()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/104276

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.0.5 -m "<description of version>" 3753babef3a7cb9840b824c4a3412d0357e4a419
git push origin v0.0.5

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/104576

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.6 -m "<description of version>" b07b5fbb8dbddb1d686bd5a3c7a63b7053d2d5c7
git push origin v0.0.6

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/104614

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.7 -m "<description of version>" fbba2ea838c858035b4aa3f794ce9615dcec4ff5
git push origin v0.0.7

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/104785

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.8 -m "<description of version>" e5698545ac14df8cc33b546e1156a18e828e5e2d
git push origin v0.0.8

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/104852

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.9 -m "<description of version>" 6489843ef006b1684a0b034c18c7c33921733e12
git push origin v0.0.9

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/106206

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.10 -m "<description of version>" afc6257259da4c8245fb156a8987e99edc3844ef
git push origin v0.0.10

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/106207

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.11 -m "<description of version>" 1680412a570829cbc6ea30ca36d7538e6afbf981
git push origin v0.0.11

[ufechner7]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/106242

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

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.0.12 -m "<description of version>" ed3b13eeaeb499a25a143b4fe268f7dd70a03418
git push origin v0.0.12

[ufechner7]

@JuliaRegistrator register

Release notes:

• improved README.md
• improved examples

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111928

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.1.0 -m "<description of version>" e0da5144f92a3fdcaa32e8be3a1e2f4fafa55839
git push origin v0.1.0

[ufechner7]

@JuliaRegistrator register

Release notes:

• add plot with dual Y axis

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/112386

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.1.1 -m "<description of version>" 69c2bd2c8c7845586c413b0eb41a414a99579631
git push origin v0.1.1

[ufechner7]

@JuliaRegistrator register

Release notes:

• two time series on the first Y axis now possible

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/112387

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.1.2 -m "<description of version>" 3e3db144fedaa2fcaa1cb6c7473855e6bb85adb3
git push origin v0.1.2

[ufechner7]

@JuliaRegistrator register

Release notes:

• add a version of plot2d() that accepts a Matrix as first parameter

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/112395

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.1.3 -m "<description of version>" e00236a5d054bd7b44cbeea8d834d9fd466d04ac
git push origin v0.1.3

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/112395

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.1.3 -m "<description of version>" df8638148d2574a50e4ec6dd69def49fc4132528
git push origin v0.1.3

[ufechner7]

@JuliaRegistrator register

Release notes:

• plot2d now also accepts an SVector as parameter

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/112444

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.1.4 -m "<description of version>" 5d52b97919e8765d8e711d9df9df4f51caaa1cd3
git push origin v0.1.4

[ufechner7]

@JuliaRegistrator register

Release notes:

Added:

• add example multi-channel-dual.jl and make it work

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/112602

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.1.5 -m "<description of version>" 1e5380d5ca7dbd2e67f95129bdf6728a5ef37c0c
git push origin v0.1.5

[ufechner7]

@JuliaRegistrator register

Release notes:

• add parameter yzoom to function plotx(); set it to a value < 1.0 for more than 6 vertical plots

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/113776

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.1.6 -m "<description of version>" 7346c617aeb30fee64b45e62279724491efcfc68
git push origin v0.1.6

[ufechner7]

@JuliaRegistrator register

Release notes:

• bump package JLD2 to version 0.5 (breaking)
• the parameter ylims is now working for plots with two y axis

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/115236

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.2.0 -m "<description of version>" 3e530af4538994500994920073162e64fa2d472d
git push origin v0.2.0

[ufechner7]

@JuliaRegistrator register

Release notes:

• the parameter scatter is now working for all variants of the plot function

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/115490

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.2.1 -m "<description of version>" e9134ecbbe8529638378ec8be9f80679201f2e56
git push origin v0.2.1