Pyomeca

When dealing with the time, it is easy to get forget when it is! Pyomeca is no longer confused by the time while dealing with time data. It can parse, move and filter them but never loose track of time.

Most of the filters now returns valid TimeFrameDependentArray, facilitating chaining and plotting of data

As a piece of code, I often forget that you, human, don't speak so much by numbers! So I've decided to facilitate our communications when you want to slice the data in me! No need to know the indexes of data you want to slice anymore, tell me their name, I'll take care of the rest.
You want a slice of me? Take it!

Release_1.11.2
Matlab users behold! Your time of easyness has finally come! After all these years of being left behind by us, you finally can enjoy biorbd without the struggle to install biorbd by yourself, as the binaries are now provided! Friends, enjoy!

What's Changed
* Added dampings to joints by pariterre in https://github.com/pyomeca/biorbd/pull/350
* Added matlab to github actions by pariterre in https://github.com/pyomeca/biorbd/pull/352


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.11.1...Release_1.11.2

Release_1.11.1
Casadi was slightly (very) cautious about making sure it was not forgetting at all to update every single time a function was called and every for loop... It was making it crazy slow for no reason. We loosened this psychorigid behavior. Casadi is now updating only what is required

What's Changed
* Added bunch of accessor so Casadi is not so slow! by pariterre in https://github.com/pyomeca/biorbd/pull/349


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.11.0...Release_1.11.1

Release_1.11.0
Each individual is unique and that is the beauty of life! Biorbd struggled with that uniqueness and decided that everyone should be the same... We taught Biorbd to recognize and embrace uniqueness when casadi is used. Now, models do not retrointeract when you call functions!

What's Changed
* Extra doc setLocalJCS by Ipuch in https://github.com/pyomeca/biorbd/pull/345
* Fixed matlab compilation issue by pariterre in https://github.com/pyomeca/biorbd/pull/346
* Added a setter for the markers by pariterre in https://github.com/pyomeca/biorbd/pull/347
* Fixed casadi duplication of the model when calling methods by pariterre in https://github.com/pyomeca/biorbd/pull/348


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.5...Release_1.11.0

Release_1.10.5
There is simple task to perform sometime. Knowing if you can be seen is one of them. However biorbd did not know that. When it was drawing itself, it just hoped for the best! Now, biorbd knows! if it has mesh or not

What's Changed
* Added path for all STL files by pariterre in https://github.com/pyomeca/biorbd/pull/342


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.4...Release_1.10.5

Release_1.10.4
When people leave, they want to be remembered as much as they can. Unlike people though, data are expected to forgotten when they leave. But Python was holding hard to that data. We thought Python to let it go.... and fixed the memory leak!

What's Changed
* Fixed memory leak when using to_array() in python by pariterre in https://github.com/pyomeca/biorbd/pull/341


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.2...Release_1.10.4

Release_1.10.2
Boris told us that he was invincible, but still he was visible. For some reason, biorbd thought that a segment who was invisible was also invincible, but now it knows... being invisible is not a prerequisite to be vincible.

What's Changed
* Fixed adding force to non dof segment by pariterre in https://github.com/pyomeca/biorbd/pull/338
* Removed a buggy loop in dispatching forces by pariterre in https://github.com/pyomeca/biorbd/pull/339


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.1...Release_1.10.2

Release_1.10.1
Don't treat person as objects, but you can for objects! External forces is now a full object in biorbd allowing for multiple interesting stuff such as transporting it from local to global coordinate system, or applying to arbitrary segments

Hot fix for an error while there were more than one segment

What's Changed
* Added a swig template for vector<size_t> by pariterre in https://github.com/pyomeca/biorbd/pull/333
* Fixed external forces addInSegmentReferenceFrame for segment not being the first by pariterre in https://github.com/pyomeca/biorbd/pull/335
* minor doc of Inverse Kinematics by Ipuch in https://github.com/pyomeca/biorbd/pull/337


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.0...Release_1.10.1

Release_1.10.0
Don't treat person as objects, but you can for objects! External forces is now a full object in biorbd allowing for multiple interesting stuff such as transporting it from local to global coordinate system, or applying to arbitrary segments

What's Changed
* Update README.md by Ipuch in https://github.com/pyomeca/biorbd/pull/330
* External forces as an object by pariterre in https://github.com/pyomeca/biorbd/pull/332
* external_force_helper by Ipuch in https://github.com/pyomeca/biorbd/pull/331


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.10...Release_1.10.0

Release_1.9.10
As we grow, we change. That was the spirit of the TMNT! Now, biorbd accepts to get more mature as time goes. You can now change the orientation of the segments after a model was loaded.

Long live to maturity

What's Changed
* Create release_checklist.md by Ipuch in https://github.com/pyomeca/biorbd/pull/320
* Update README.md by Ipuch in https://github.com/pyomeca/biorbd/pull/321
* Added the capability to slice kalman filter before filtering by pariterre in https://github.com/pyomeca/biorbd/pull/322
* Update read, add actuator information by AnaisFarr in https://github.com/pyomeca/biorbd/pull/319
* [RTR] loop constraints by Ipuch in https://github.com/pyomeca/biorbd/pull/323
* [RTR] set LocalJCS of segments by Ipuch in https://github.com/pyomeca/biorbd/pull/327

New Contributors
* AnaisFarr made their first contribution in https://github.com/pyomeca/biorbd/pull/319

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.9...Release_1.9.10

Release_1.9.9
Let's say you want to hold a beer, you would need muscles, of course. But at some points, you won't hold long enough if passive forces from your ligaments are not involved! Biorbd now allows you to hold your beer as long as you want by modeling the ligaments.

What's Changed
* [RTR] Total energy and Lagrangian by Ipuch in https://github.com/pyomeca/biorbd/pull/311
* yxy rotation by rapidnico in https://github.com/pyomeca/biorbd/pull/314
* [almost RTM] Passive torque by aceglia in https://github.com/pyomeca/biorbd/pull/312
* [WIP] Add ligaments by aceglia in https://github.com/pyomeca/biorbd/pull/315

New Contributors
* rapidnico made their first contribution in https://github.com/pyomeca/biorbd/pull/314

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.8...Release_1.9.9

Release_1.9.8
Biorbd has this huge potential (energy), it moves and bounces around computing kinetic (energy). But it keeps all this potential (energy) for itself. Now, it exposes it to the world! Computation for kinetic and potential energy are now interfaced for Python

What's Changed
* Fixed the non working "copy" function on np.array on Linux by pariterre in https://github.com/pyomeca/biorbd/pull/307
* [RTR] kinetic and potential energy interfaced with rbdl by Ipuch in https://github.com/pyomeca/biorbd/pull/308
* Bug from transposing in Python by pariterre in https://github.com/pyomeca/biorbd/pull/309
* Made Python marker more resilient to the absence of parent name by pariterre in https://github.com/pyomeca/biorbd/pull/310


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.7...Release_1.9.8

Release_1.9.7
With hopes come despair... but also renewing with hopes! We had been a bit to much happy to release, now it is actually ready

What's Changed
* Properly reordered the swig interface to account for muscles by pariterre in https://github.com/pyomeca/biorbd/pull/306


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.6...Release_1.9.7

Release_1.9.6
Restarting not from the beginning, that is what A New Hope taught us! Here we are... doing the same thing but slightly better. This brings us hope for a brighter future

What's Changed
* Added an actual mean computation for the matrix rotation in Python by pariterre in https://github.com/pyomeca/biorbd/pull/302
* Tried Github actions by pariterre in https://github.com/pyomeca/biorbd/pull/303
* Tried Github actions by pariterre in https://github.com/pyomeca/biorbd/pull/304
* Fixed a reference bug that was randomly transposing matrices by pariterre in https://github.com/pyomeca/biorbd/pull/305
* Move actuators and muscles in "internalforce" namespace by aceglia in https://github.com/pyomeca/biorbd/pull/301


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.5...Release_1.9.6

Release_1.9.5
Grooving too much is tiring. But biorbd could do it endlessly! It is now possible to compute the tiringness of biorbd when grooving with DeGroote

What's Changed
* [RTR] Add degrootefatiguable and degrooteactive only by aceglia in https://github.com/pyomeca/biorbd/pull/298


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.4...Release_1.9.5

Release_1.9.4
Dancing can be trilling, it can also be deceiving. When you go too fast too soon, you make mistake. DeGroote was way too groovy and is now more in phase with reality.

What's Changed
* Change velocity normalization for degroote muscle type by aceglia in https://github.com/pyomeca/biorbd/pull/295


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.3...Release_1.9.4

Release_1.9.3
Groovy is the science advancing. DeGroote is the latest muscle model that joined the biorbd suite! With that, let you model dance on the Groove!

Release_1.9.2
Groovy is the science advancing. DeGroote is the latest muscle model that joined the biorbd suite! With that, let you model dance on the Groove!

What's Changed
* Fixed a bug in Kalman by pariterre in https://github.com/pyomeca/biorbd/pull/291
* Replaced translations/rotations litteral for enums by pariterre in https://github.com/pyomeca/biorbd/pull/292
* Based muscle on reference and add degroote type by aceglia in https://github.com/pyomeca/biorbd/pull/250


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.1...Release_1.9.2

Release_1.9.1
Who hasn't dreamed of being a top model? The most beautiful being out there!
Since you'll never be able to achieve that goal, biorbd now allows you to easily create any model you want! And who knows, if you work hard enough, maybe you'll create the most beautiful model out there! (I must admit, I doubt it though...)

What's Changed
* Jacobian of segment rotation matrix by Ipuch in https://github.com/pyomeca/biorbd/pull/284
* added yzy rotation to Rotation.toEulerAngles by EveCharbie in https://github.com/pyomeca/biorbd/pull/287
* Simplified the model creation for segment by pariterre in https://github.com/pyomeca/biorbd/pull/286
* Made better message by pariterre in https://github.com/pyomeca/biorbd/pull/290


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.0...Release_1.9.1

Release_1.9.0
You want to design new models easily? There are now a python interface to do that. Welcome to modernity!

What's Changed
* [RTR] Added a check to make sure nbRoot > 0 by Sciancisco in https://github.com/pyomeca/biorbd/pull/281
* generalizing contacts to forward dynamics by Ipuch in https://github.com/pyomeca/biorbd/pull/278
* Improved version of ToSpatialVector by pariterre in https://github.com/pyomeca/biorbd/pull/282
* [RTR] eulerDot - body velocity tranformation by EveCharbie in https://github.com/pyomeca/biorbd/pull/263
* Model creation in python by pariterre in https://github.com/pyomeca/biorbd/pull/283


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.8...Release_1.9.0

Release_1.8.8
Python is a higher, but sometime things slow down... A round about is therefore always welcome!
Biorbd can now call multiply on native matrix for, for instance, rotate

What's Changed
* Add free floating dynamics by Sciancisco in https://github.com/pyomeca/biorbd/pull/276
* add the class InverseKinematics by AurelienRenou in https://github.com/pyomeca/biorbd/pull/274
* Added the capability to multiply in python by pariterre in https://github.com/pyomeca/biorbd/pull/279

New Contributors
* Sciancisco made their first contribution in https://github.com/pyomeca/biorbd/pull/276
* AurelienRenou made their first contribution in https://github.com/pyomeca/biorbd/pull/274

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.7...Release_1.8.8

Release_1.8.7
Windows...

What's Changed
* Bug fix in AddContact since new RBDL API by pariterre in https://github.com/pyomeca/biorbd/pull/262
* Update README.md by nashmit in https://github.com/pyomeca/biorbd/pull/266
* compute angular velocity around CoM by EveCharbie in https://github.com/pyomeca/biorbd/pull/261
* possibility to add variables in RT assign by EveCharbie in https://github.com/pyomeca/biorbd/pull/270
* Fixed for conda-forge using VS2017 by pariterre in https://github.com/pyomeca/biorbd/pull/272

New Contributors
* nashmit made their first contribution in https://github.com/pyomeca/biorbd/pull/266

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.6...Release_1.8.7

Release_1.8.6
Windows...

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.5...Release_1.8.6

Release_1.8.5
Biorbd is doing fancy stuff, but when asked how many markers on a segment, it could not provided a proper answer! It now learn how to count properly

What's Changed
* Handling inverse dynamics with rigid contact by Ipuch in https://github.com/pyomeca/biorbd/pull/251
* Added mesh properties in ModelWriter (meshcolor, meshscale, meshrt) by RVSagar in https://github.com/pyomeca/biorbd/pull/254
* Analytical Inverse of the Joint Space Inertia Matrix by Ipuch in https://github.com/pyomeca/biorbd/pull/255
* Fixed nbMarkers per segment by pariterre in https://github.com/pyomeca/biorbd/pull/258

New Contributors
* RVSagar made their first contribution in https://github.com/pyomeca/biorbd/pull/254

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.4...Release_1.8.5

Release_1.8.4
Even though the soft is the new rigid, it is not a reason not to be able to acquire the rigid contact as expected. New accessors were added to the rigid contacts

What's Changed
* GetBodyRbdlId added as a function for Python users. by Ipuch in https://github.com/pyomeca/biorbd/pull/248
* Fixed a bug in FlPE introduced when changed muscle length by pariterre in https://github.com/pyomeca/biorbd/pull/247
* Enhanced rigid contact API by Ipuch in https://github.com/pyomeca/biorbd/pull/249


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.3...Release_1.8.4

Release_1.8.3
In war as in war! When things disperse they lose track of reality. Biorbd now has a way to regroup all forces at a single point so they can force together to win the dynamics battle

What's Changed
* Fixed a matlab error by pariterre in https://github.com/pyomeca/biorbd/pull/243
* Let's make friction coefficients editable by Ipuch in https://github.com/pyomeca/biorbd/pull/242
* Added a set method to inertia by pariterre in https://github.com/pyomeca/biorbd/pull/246
* ComputeForceAtOrigin available for python by Ipuch in https://github.com/pyomeca/biorbd/pull/244


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.2...Release_1.8.3

Release_1.8.2
The perpetual motion does not exist. Biorbd is sad about that... So when using the soft contact, she decided to create energy at each impact. While it is promising for the future of the planet, it is fairly unrealistic. We decided to cut Biorbd's dream to ground her in the reality. Sorry Biorbd, you are more realistic now

What's Changed
* SoftContact torque applied in world frame. by Ipuch in https://github.com/pyomeca/biorbd/pull/240

Release_1.8.1
The previous version of biorbd knew about the soft contact, but was not using them.. after all, they are soft!
But not so soft!

What's Changed
* Fixed bug in forces distribution for soft contact by pariterre in https://github.com/pyomeca/biorbd/pull/238


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.0...Release_1.8.1

Release_1.8.0
Who doesn't like baseball? Biorbd has now learn soft ball and cannot live without it anymore!
The soft ball constraints can be used to add forces as a replacement of contact dynamics!

Hit the ball and run around the diamond, you just made an homerun biorbd!

Release_1.7.4
Mesh file are not always congruent to the segment attached to. One problem with that is that it can be impossible to use a mesh file. Now, it is possible to rotate/translation/scale a mesh directly in the bioMod!

Enjoy your mesh!

Release_1.7.3
Biorbd has style! But recently has got even more style! Mainly style of writing mesh format! STL is now available :D

Release_1.11.2
Matlab users behold! Your time of easyness has finally come! After all these years of being left behind by us, you finally can enjoy biorbd without the struggle to install biorbd by yourself, as the binaries are now provided! Friends, enjoy!

What's Changed
* Added dampings to joints by pariterre in https://github.com/pyomeca/biorbd/pull/350
* Added matlab to github actions by pariterre in https://github.com/pyomeca/biorbd/pull/352


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.11.1...Release_1.11.2

Release_1.11.1
Casadi was slightly (very) cautious about making sure it was not forgetting at all to update every single time a function was called and every for loop... It was making it crazy slow for no reason. We loosened this psychorigid behavior. Casadi is now updating only what is required

What's Changed
* Added bunch of accessor so Casadi is not so slow! by pariterre in https://github.com/pyomeca/biorbd/pull/349


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.11.0...Release_1.11.1

Release_1.11.0
Each individual is unique and that is the beauty of life! Biorbd struggled with that uniqueness and decided that everyone should be the same... We taught Biorbd to recognize and embrace uniqueness when casadi is used. Now, models do not retrointeract when you call functions!

What's Changed
* Extra doc setLocalJCS by Ipuch in https://github.com/pyomeca/biorbd/pull/345
* Fixed matlab compilation issue by pariterre in https://github.com/pyomeca/biorbd/pull/346
* Added a setter for the markers by pariterre in https://github.com/pyomeca/biorbd/pull/347
* Fixed casadi duplication of the model when calling methods by pariterre in https://github.com/pyomeca/biorbd/pull/348


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.5...Release_1.11.0

Release_1.10.5
There is simple task to perform sometime. Knowing if you can be seen is one of them. However biorbd did not know that. When it was drawing itself, it just hoped for the best! Now, biorbd knows! if it has mesh or not

What's Changed
* Added path for all STL files by pariterre in https://github.com/pyomeca/biorbd/pull/342


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.4...Release_1.10.5

Release_1.10.4
When people leave, they want to be remembered as much as they can. Unlike people though, data are expected to forgotten when they leave. But Python was holding hard to that data. We thought Python to let it go.... and fixed the memory leak!

What's Changed
* Fixed memory leak when using to_array() in python by pariterre in https://github.com/pyomeca/biorbd/pull/341


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.2...Release_1.10.4

Release_1.10.2
Boris told us that he was invincible, but still he was visible. For some reason, biorbd thought that a segment who was invisible was also invincible, but now it knows... being invisible is not a prerequisite to be vincible.

What's Changed
* Fixed adding force to non dof segment by pariterre in https://github.com/pyomeca/biorbd/pull/338
* Removed a buggy loop in dispatching forces by pariterre in https://github.com/pyomeca/biorbd/pull/339


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.1...Release_1.10.2

Release_1.10.1
Don't treat person as objects, but you can for objects! External forces is now a full object in biorbd allowing for multiple interesting stuff such as transporting it from local to global coordinate system, or applying to arbitrary segments

Hot fix for an error while there were more than one segment

What's Changed
* Added a swig template for vector<size_t> by pariterre in https://github.com/pyomeca/biorbd/pull/333
* Fixed external forces addInSegmentReferenceFrame for segment not being the first by pariterre in https://github.com/pyomeca/biorbd/pull/335
* minor doc of Inverse Kinematics by Ipuch in https://github.com/pyomeca/biorbd/pull/337


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.10.0...Release_1.10.1

Release_1.10.0
Don't treat person as objects, but you can for objects! External forces is now a full object in biorbd allowing for multiple interesting stuff such as transporting it from local to global coordinate system, or applying to arbitrary segments

What's Changed
* Update README.md by Ipuch in https://github.com/pyomeca/biorbd/pull/330
* External forces as an object by pariterre in https://github.com/pyomeca/biorbd/pull/332
* external_force_helper by Ipuch in https://github.com/pyomeca/biorbd/pull/331


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.10...Release_1.10.0

Release_1.9.10
As we grow, we change. That was the spirit of the TMNT! Now, biorbd accepts to get more mature as time goes. You can now change the orientation of the segments after a model was loaded.

Long live to maturity

What's Changed
* Create release_checklist.md by Ipuch in https://github.com/pyomeca/biorbd/pull/320
* Update README.md by Ipuch in https://github.com/pyomeca/biorbd/pull/321
* Added the capability to slice kalman filter before filtering by pariterre in https://github.com/pyomeca/biorbd/pull/322
* Update read, add actuator information by AnaisFarr in https://github.com/pyomeca/biorbd/pull/319
* [RTR] loop constraints by Ipuch in https://github.com/pyomeca/biorbd/pull/323
* [RTR] set LocalJCS of segments by Ipuch in https://github.com/pyomeca/biorbd/pull/327

New Contributors
* AnaisFarr made their first contribution in https://github.com/pyomeca/biorbd/pull/319

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.9...Release_1.9.10

Release_1.9.9
Let's say you want to hold a beer, you would need muscles, of course. But at some points, you won't hold long enough if passive forces from your ligaments are not involved! Biorbd now allows you to hold your beer as long as you want by modeling the ligaments.

What's Changed
* [RTR] Total energy and Lagrangian by Ipuch in https://github.com/pyomeca/biorbd/pull/311
* yxy rotation by rapidnico in https://github.com/pyomeca/biorbd/pull/314
* [almost RTM] Passive torque by aceglia in https://github.com/pyomeca/biorbd/pull/312
* [WIP] Add ligaments by aceglia in https://github.com/pyomeca/biorbd/pull/315

New Contributors
* rapidnico made their first contribution in https://github.com/pyomeca/biorbd/pull/314

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.8...Release_1.9.9

Release_1.9.8
Biorbd has this huge potential (energy), it moves and bounces around computing kinetic (energy). But it keeps all this potential (energy) for itself. Now, it exposes it to the world! Computation for kinetic and potential energy are now interfaced for Python

What's Changed
* Fixed the non working "copy" function on np.array on Linux by pariterre in https://github.com/pyomeca/biorbd/pull/307
* [RTR] kinetic and potential energy interfaced with rbdl by Ipuch in https://github.com/pyomeca/biorbd/pull/308
* Bug from transposing in Python by pariterre in https://github.com/pyomeca/biorbd/pull/309
* Made Python marker more resilient to the absence of parent name by pariterre in https://github.com/pyomeca/biorbd/pull/310


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.7...Release_1.9.8

Release_1.9.7
With hopes come despair... but also renewing with hopes! We had been a bit to much happy to release, now it is actually ready

What's Changed
* Properly reordered the swig interface to account for muscles by pariterre in https://github.com/pyomeca/biorbd/pull/306


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.6...Release_1.9.7

Release_1.9.6
Restarting not from the beginning, that is what A New Hope taught us! Here we are... doing the same thing but slightly better. This brings us hope for a brighter future

What's Changed
* Added an actual mean computation for the matrix rotation in Python by pariterre in https://github.com/pyomeca/biorbd/pull/302
* Tried Github actions by pariterre in https://github.com/pyomeca/biorbd/pull/303
* Tried Github actions by pariterre in https://github.com/pyomeca/biorbd/pull/304
* Fixed a reference bug that was randomly transposing matrices by pariterre in https://github.com/pyomeca/biorbd/pull/305
* Move actuators and muscles in "internalforce" namespace by aceglia in https://github.com/pyomeca/biorbd/pull/301


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.5...Release_1.9.6

Release_1.9.5
Grooving too much is tiring. But biorbd could do it endlessly! It is now possible to compute the tiringness of biorbd when grooving with DeGroote

What's Changed
* [RTR] Add degrootefatiguable and degrooteactive only by aceglia in https://github.com/pyomeca/biorbd/pull/298


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.4...Release_1.9.5

Release_1.9.4
Dancing can be trilling, it can also be deceiving. When you go too fast too soon, you make mistake. DeGroote was way too groovy and is now more in phase with reality.

What's Changed
* Change velocity normalization for degroote muscle type by aceglia in https://github.com/pyomeca/biorbd/pull/295


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.3...Release_1.9.4

Release_1.9.3
Groovy is the science advancing. DeGroote is the latest muscle model that joined the biorbd suite! With that, let you model dance on the Groove!

Release_1.9.2
Groovy is the science advancing. DeGroote is the latest muscle model that joined the biorbd suite! With that, let you model dance on the Groove!

What's Changed
* Fixed a bug in Kalman by pariterre in https://github.com/pyomeca/biorbd/pull/291
* Replaced translations/rotations litteral for enums by pariterre in https://github.com/pyomeca/biorbd/pull/292
* Based muscle on reference and add degroote type by aceglia in https://github.com/pyomeca/biorbd/pull/250


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.1...Release_1.9.2

Release_1.9.1
Who hasn't dreamed of being a top model? The most beautiful being out there!
Since you'll never be able to achieve that goal, biorbd now allows you to easily create any model you want! And who knows, if you work hard enough, maybe you'll create the most beautiful model out there! (I must admit, I doubt it though...)

What's Changed
* Jacobian of segment rotation matrix by Ipuch in https://github.com/pyomeca/biorbd/pull/284
* added yzy rotation to Rotation.toEulerAngles by EveCharbie in https://github.com/pyomeca/biorbd/pull/287
* Simplified the model creation for segment by pariterre in https://github.com/pyomeca/biorbd/pull/286
* Made better message by pariterre in https://github.com/pyomeca/biorbd/pull/290


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.9.0...Release_1.9.1

Release_1.9.0
You want to design new models easily? There are now a python interface to do that. Welcome to modernity!

What's Changed
* [RTR] Added a check to make sure nbRoot > 0 by Sciancisco in https://github.com/pyomeca/biorbd/pull/281
* generalizing contacts to forward dynamics by Ipuch in https://github.com/pyomeca/biorbd/pull/278
* Improved version of ToSpatialVector by pariterre in https://github.com/pyomeca/biorbd/pull/282
* [RTR] eulerDot - body velocity tranformation by EveCharbie in https://github.com/pyomeca/biorbd/pull/263
* Model creation in python by pariterre in https://github.com/pyomeca/biorbd/pull/283


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.8...Release_1.9.0

Release_1.8.8
Python is a higher, but sometime things slow down... A round about is therefore always welcome!
Biorbd can now call multiply on native matrix for, for instance, rotate

What's Changed
* Add free floating dynamics by Sciancisco in https://github.com/pyomeca/biorbd/pull/276
* add the class InverseKinematics by AurelienRenou in https://github.com/pyomeca/biorbd/pull/274
* Added the capability to multiply in python by pariterre in https://github.com/pyomeca/biorbd/pull/279

New Contributors
* Sciancisco made their first contribution in https://github.com/pyomeca/biorbd/pull/276
* AurelienRenou made their first contribution in https://github.com/pyomeca/biorbd/pull/274

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.7...Release_1.8.8

Release_1.8.7
Windows...

What's Changed
* Bug fix in AddContact since new RBDL API by pariterre in https://github.com/pyomeca/biorbd/pull/262
* Update README.md by nashmit in https://github.com/pyomeca/biorbd/pull/266
* compute angular velocity around CoM by EveCharbie in https://github.com/pyomeca/biorbd/pull/261
* possibility to add variables in RT assign by EveCharbie in https://github.com/pyomeca/biorbd/pull/270
* Fixed for conda-forge using VS2017 by pariterre in https://github.com/pyomeca/biorbd/pull/272

New Contributors
* nashmit made their first contribution in https://github.com/pyomeca/biorbd/pull/266

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.6...Release_1.8.7

Release_1.8.6
Windows...

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.5...Release_1.8.6

Release_1.8.5
Biorbd is doing fancy stuff, but when asked how many markers on a segment, it could not provided a proper answer! It now learn how to count properly

What's Changed
* Handling inverse dynamics with rigid contact by Ipuch in https://github.com/pyomeca/biorbd/pull/251
* Added mesh properties in ModelWriter (meshcolor, meshscale, meshrt) by RVSagar in https://github.com/pyomeca/biorbd/pull/254
* Analytical Inverse of the Joint Space Inertia Matrix by Ipuch in https://github.com/pyomeca/biorbd/pull/255
* Fixed nbMarkers per segment by pariterre in https://github.com/pyomeca/biorbd/pull/258

New Contributors
* RVSagar made their first contribution in https://github.com/pyomeca/biorbd/pull/254

**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.4...Release_1.8.5

Release_1.8.4
Even though the soft is the new rigid, it is not a reason not to be able to acquire the rigid contact as expected. New accessors were added to the rigid contacts

What's Changed
* GetBodyRbdlId added as a function for Python users. by Ipuch in https://github.com/pyomeca/biorbd/pull/248
* Fixed a bug in FlPE introduced when changed muscle length by pariterre in https://github.com/pyomeca/biorbd/pull/247
* Enhanced rigid contact API by Ipuch in https://github.com/pyomeca/biorbd/pull/249


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.3...Release_1.8.4

Release_1.8.3
In war as in war! When things disperse they lose track of reality. Biorbd now has a way to regroup all forces at a single point so they can force together to win the dynamics battle

What's Changed
* Fixed a matlab error by pariterre in https://github.com/pyomeca/biorbd/pull/243
* Let's make friction coefficients editable by Ipuch in https://github.com/pyomeca/biorbd/pull/242
* Added a set method to inertia by pariterre in https://github.com/pyomeca/biorbd/pull/246
* ComputeForceAtOrigin available for python by Ipuch in https://github.com/pyomeca/biorbd/pull/244


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.2...Release_1.8.3

Release_1.8.2
The perpetual motion does not exist. Biorbd is sad about that... So when using the soft contact, she decided to create energy at each impact. While it is promising for the future of the planet, it is fairly unrealistic. We decided to cut Biorbd's dream to ground her in the reality. Sorry Biorbd, you are more realistic now

What's Changed
* SoftContact torque applied in world frame. by Ipuch in https://github.com/pyomeca/biorbd/pull/240

Release_1.8.1
The previous version of biorbd knew about the soft contact, but was not using them.. after all, they are soft!
But not so soft!

What's Changed
* Fixed bug in forces distribution for soft contact by pariterre in https://github.com/pyomeca/biorbd/pull/238


**Full Changelog**: https://github.com/pyomeca/biorbd/compare/Release_1.8.0...Release_1.8.1

Release_1.8.0
Who doesn't like baseball? Biorbd has now learn soft ball and cannot live without it anymore!
The soft ball constraints can be used to add forces as a replacement of contact dynamics!

Hit the ball and run around the diamond, you just made an homerun biorbd!

Release_1.7.4
Mesh file are not always congruent to the segment attached to. One problem with that is that it can be impossible to use a mesh file. Now, it is possible to rotate/translation/scale a mesh directly in the bioMod!

Enjoy your mesh!

Release_1.7.3
Biorbd has style! But recently has got even more style! Mainly style of writing mesh format! STL is now available :D

Release_1.7.2
Wrappings objects were having some issues, but thanks to a new contributor, it is now fixed!

Release_1.7.1
For some reason, biorbd though segments without inertia should be heavy... It now knows better!

Please be aware that this fix will greatly changes the result if you were computing forward dynamics with segments that did not have inertia matrix!

Release_1.7.0
Casadi and Eigen have been brothers, but could not stand each others. Now that they have separate rooms (namespace) they can be bros again!

Release_1.6.1
RBDL entered a new era, so biorbd.
Enjoy the re-eMERGing of rbdl with its predecessor :)

Release_1.6.0
RBDL moved forward, let's follow it!

Release_1.5.5
The universe expansion is a hard fact that no one can escape. So is expanding Casadi function. But something for both it creates disturbance and should therefore be avoided.

The Python interface can now expand or not depending on the will of the user

Release_1.5.4
MX are sometime hard to use. Biorbd has an actual Python interface, but was not so much convenient. It is now a bit easier to use!

Release_1.5.3
Getting the index of markers and segments in Python was a bit cumbersome. You now can ask directly to biorbd!

Release_1.5.2
Scalar are 1x1 matrices, or are they? Biorbd doesn't ask this question anymore and answers yes. Therefore it is now possible to create a scalar from a numpy 1x1 array

Release_1.5.1
A vector 3d is the basics of 3d geometry. Yet Python didn't like them very much... This is now something from the past as Python can now use directly native numpy and DM vectors to declare a 3d Vector! Hurray :D

Release_1.5.0
The wrappings have been revived! Hurray! So now the muscles are able to wrap around a half cylinder. This is modest but, hey!, that is a good start :)

Release_1.4.4
The way to provided muscle states was... confusing.. the least to say! Now, there is only two ways, the good way or the high way, as in the United States. So the muscle states now comes in a united way using the stateSet function

Release_1.4.3
Even though you don't need to Release, you kind of need to anyway...
That is the art of the Zenodo's paradox!

Release_1.4.2
CasADi is now Windows friendly!

Release_1.4.1
`biorbd` made itself pretty for the journal! It is now ready to be publish :D

Release_1.4.0
It is important to build on the past, but at some point, you have to make sure to start fresh. Casadi was a bit too much confident with the past. It now updates the kinematics all the time. This takes a bit of time, but gives you much better results!

This update may change previous results. This is why it is a full minor change

Release_1.3.7
When you like to move it move it, you never want the music to stop! Biorbd was a bit stiff, and did not like you to move it move it.
Now, biorbd lets you dance as you wish by not SegFaulting if you move a marker by hand!

Release_1.3.6
Walking forward should be as good as walking backward. If you have two API for the same purpose, it gets highly confusing. While it is funny to watch confused people, it is not very practical...
Biorbd now uses the same API for InverseDynamics and ForwardDynamics. Hurray!

Release_1.3.5
Casadi function are not just for SX but also MX and (more importantly!) for DM as well. The name for the casadi function interface better reflects that :)

Release_1.3.4
The forces and mouvements may lie in complete different mathematical environment (yep... maths are weird...)
Biorbd was computing the sizes of these environment wrongly... That is no more the case! GeneralizedTorque is has now the right size :)

Release_1.3.3
When changing mass feature, some things must be change as well, such as Inertia. Biorbd was ignoring the real things, but it does no more! While you change the segment characteristics, it now updates matrix of inertia

Release_1.3.2
QRanges was only in awe with Euler. Despite Euler's massive contribution to... everything?... Hamilton, must not be forgot! Quaternion are important even though they are impossible to interpret and pretty much useless... Some people like it... whatever...
Now QRanges like quaternions as well :D and won't simply fail if you define quaternions in your model!

Release_1.3.1
"That is a pretty library, but I don't know what to do with it" is no longer something you should say! `biorbd` is now filled with examples for C++, MATLAB and Python! These examples are a complete example of the inverse flow (inverse kinematics, inverse dynamics and static optimization) and of the direct flow (muscle forces, forward dynamics and forward kinematics).

So now you know what I've got!

Release_1.3.0
Faster, higher and Stronger!

Biorbd continuously evolves to get better speed, reaching higher standard and simulating stronger models. Enjoy this revamped version of biorbd :)

Release_1.2.9
All things considered, all break down to the interaction to the environment. Biorbd gets better and better to interact with environment thanks to better muscle description and impact functions.

Special shout out to paulWegiel and leasanchez for their contributions!

Release_1.2.8
CasADi is learning more and more! It now knows how to use actuators!
Actuate good :)

Release_1.2.7
biorbd was going on with his own way of linking Python, but CMake is a big guy, no need to do the job for it. biorbd now trusts CMake to do the job (and a better job :D )

Release_1.2.6
biorbd was going on with his own way of linking Python, but CMake is a big guy, no need to do the job for it. biorbd now trusts CMake to do the job (and a better job :D )

Release_1.2.5
Muscles are not meant to be hidden, but shown to the world! biorbd is now proud of itself and gives you better access to the muscles!

Release_1.2.4
Tell me more, Tell me more!
Why would you split the data when you can give matrices? Casadi can benefit from that especially for speed puposes

Release_1.2.3
Every tactician will tell, information is key! So why would biorbd hides information from you? That is a big question. No hiding anymore. Unleash the power of being well inform on where you are from for both version of biorbd and bioMod file opened.

But remember, with great power comes great responsability

Release_1.2.2
Windows allows for big files, but only if that option is given.

Release_1.2.1
Ever wonder if that CasADillas was good or bad? Out-of-date? Don't worry no more. The CasADi backend is now as fully tested as the Eigen3 backend.

So eat that CasADillas without fear!

Release_1.2.0
What did you say? I said CasADi! Automatic differentiation!
You want to have the derivative of inverse dynamics? Got it! You want to have derivative of forward dynamics? Got it too! Actually, you can have the derivative of any function within biorbd, just compile it with the great CasADi tag :)

Have a look https://web.casadi.org/


Release_1.1.3
Don't hide your mass anymore, like yourself.
biorbd doesn't hide its mass matrix anymore to Python!

Release_1.1.2
There are risks going blindly into the wild not knowing what you can handle! Knowing your personal limits allows to safely explore and understand the world, and maybe overpass these limits without getting hurt in the process!

biorbd now knows the limit of the GeneralizedCoordinates so the avatars can safely explore their virtual world without breaking their virtual bones.

Long live to the safe explorer

Release_1.1.1
Sometime you have to pimp your snake so it doesn't cripple when it tries to fly by itself! With this release, Python can rotate and transrotate alone, no help, like a full grown snake of his own!

Release_1.1.0
Do you want to be babysit? Honestly, I cannot decide for you... So now biorbd won't make that decision for you! you can turn on several assert if you want to be sure that the dimensions of the vector you use are right. This comes with lower performance though. So, as a full grown human, you can decide to live dangerously and turn off these helps. This comes with performance improvements, but risks of segmentation fault (Duh...)

So, which type of person are you? Fast or safe?

Release_1.0.1
Look forward, but never forget where you are from. Sometime you need low level stuff and Biorbd should give it to you. Now it does! The C interface has been revived and is now fully functional. Not a lot of function are actually interfaced, but at least they do work.

From past to future, let all of us work hand-in-hand!

Release_1.0.0
Getting old is great, getting young is even better! Biorbd has now the wisdom of a sage embodied is a brand new youth code.

This revamping of the code is a major rewrite of biorbd. I got rid of the legacy architecture to create a better one based on module, with the unfortunate adverse effect of completely breaking backward compatibility. On the bright side though, compiling biorbd is almost 3x faster, and the code itself is also twice as fast from the previous version.

So fasten your seat belt, make some minor changes to your code and get ready for a fast biorbding!

Release_0.1.3
Biorbd is now a master snake! Python has not much secret anymore for it :)

Enjoy pythoning as much as Matlabing!

Release_0.1.2
As swig evolves, so do I! Now I can manage the version 4 of swig, which is pretty awesome :)

Release_0.1.1
Biorbd now supports travis tests on all platform! They are not written yet, but hey! You can test it if you want :)

Release_0.1.0
Small steps, crying and laughing. At that age you know what to you, but don't actually know how. Sometime biorbd feels like this. But small baby will become big!

Release_1.5.17
Ezc3d was walking down the street, abandoned by the "ez" part of its name. Sad and lonely, he was thinking... How can I be made ez again. And the light came on the form of four letters PyPI. Ezc3d worked hard, and now he is accepted on PyPI!! HipPyPI Hurray for ezc3d!

What's Changed
* Update README.md by SjoerdBruijn in https://github.com/pyomeca/ezc3d/pull/340
* Update README.md by mrrezaie in https://github.com/pyomeca/ezc3d/pull/344
* Finalized PyPI by pariterre in https://github.com/pyomeca/ezc3d/pull/348

New Contributors
* SjoerdBruijn made their first contribution in https://github.com/pyomeca/ezc3d/pull/340
* mrrezaie made their first contribution in https://github.com/pyomeca/ezc3d/pull/344

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.11...Release_1.5.17

Release_1.5.11
Matlab users behold! Your time of easyness has finally come! After all these years of being left behind by us, you finally can enjoy ezc3d without the struggle to install ezc3d by yourself, as the binaries are now provided! Friends, enjoy!

What's Changed
* Added an example how to modifiy a file in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/324
* Fixed regex for python setup install by pariterre in https://github.com/pyomeca/ezc3d/pull/329
* Fixed subframes inversion in rotation for python by pariterre in https://github.com/pyomeca/ezc3d/pull/330
* Added support for arm64 on macos for the matlab binding by pariterre in https://github.com/pyomeca/ezc3d/pull/333
* Push matlab binaries github action by pariterre in https://github.com/pyomeca/ezc3d/pull/335
* Removed useless multiple matlab compilation by pariterre in https://github.com/pyomeca/ezc3d/pull/336
* Video for Matlab binaries by Ipuch in https://github.com/pyomeca/ezc3d/pull/337


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.10...Release_1.5.11

Release_1.5.10
Something when things go south, we need to express ourselves. Ezc3d was struggling telling what was bothering it properly! Thanks this release some errors are now easier to understand

What's Changed
* Fixed computation of number of frames of Rotations in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/317
* Improved some error messages by pariterre in https://github.com/pyomeca/ezc3d/pull/322


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.9...Release_1.5.10

Release_1.5.9
When people leave, they want to be remembered as much as they can. Unlike people though, data are expected to forgotten when they leave. But Python was holding hard to that data. We thought Python to let it go.... and fixed the memory leak!

What's Changed
* Fixed memory leak when using to_array() in python by pariterre in https://github.com/pyomeca/ezc3d/pull/315


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.8...Release_1.5.9

Release_1.5.8
Once in a while, a shady company implements their version of ezc3d. Quite often, this comes with caveat as they don't fully comply to what one would call "standard". Still, ezc3d enjoys welcoming new comers! That is why, we are now embracing the Shadow implementation.
Long live to this new friendship!

What's Changed
* Made the SHADOW company sloppy implemented readable by pariterre in https://github.com/pyomeca/ezc3d/pull/309
* Disregarded the first two bytes of parameters section when reading by pariterre in https://github.com/pyomeca/ezc3d/pull/310
* Made FPCOPPOLY optional for type-3 force platforms by pariterre in https://github.com/pyomeca/ezc3d/pull/311


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.7...Release_1.5.8

Release_1.5.7
When you have something to do, you can be careful and checking again and again and again, making sure no mistake is made. But at some point, when you know things are good, as everyone know: just do it! Ezc3d can now add frames in batch so they are not verified individually but only once drastically increasing the spead of creating large files.

What's Changed
* Fixed Python from the previous update by pariterre in https://github.com/pyomeca/ezc3d/pull/304
* Fixed number of frames for nframes > 32767 and made creating them much faster by pariterre in https://github.com/pyomeca/ezc3d/pull/305


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.6...Release_1.5.7

Release_1.5.6
During is infamous discussion, Councillor Hamann says a that the one has a good point. Here in ezc3d, we always try to make good points. However, some company prefers not. As Kistler failed to have good points in their c3d, ezc3d must now make it for them!

What's Changed
* add units in Points to make it readable by mokka by Ipuch in https://github.com/pyomeca/ezc3d/pull/299
* Added capability to read Kistler's c3d files by pariterre in https://github.com/pyomeca/ezc3d/pull/302

New Contributors
* Ipuch made their first contribution in https://github.com/pyomeca/ezc3d/pull/299

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.5...Release_1.5.6

Release_1.5.5
There was a time where everything was easy, one could get water at the river and drink. Nowadays, everything is more complex. A good example is to compute the center of pressure. It could be as easy as computing it, but Kistler made it slightly more sophisticated. Ezc3d adores what is sophisticated and had a desire to compute it properly. It is now done!

What's Changed
* Typo by pariterre in https://github.com/pyomeca/ezc3d/pull/298
* Added Kistler FPCOPPOLY tag by pariterre in https://github.com/pyomeca/ezc3d/pull/297


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.4...Release_1.5.5

Release_1.5.4
With the rotation built-in, ezc3d was WAYYYYY to happy to have them in Matlab and would go crazy creating A LOOOOT of them. We had to restrict its enthousiasm.

Limitation tastes better!

What's Changed
* [RTM] MATLAB explanations by EveCharbie in https://github.com/pyomeca/ezc3d/pull/288

New Contributors
* EveCharbie made their first contribution in https://github.com/pyomeca/ezc3d/pull/288

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.3...Release_1.5.4

Release_1.5.3
Matlab is a well-known software to deal with matrices, it is basically in its name (MATrix LABoratory)!
Still, ezc3d was ignoring that fact and did not allowed to access Rotations feature on Matlab. It is now fully fixed and Matlab can be as happy as Python!

What's Changed
* Added support for files with Rotations in Matlab by pariterre in https://github.com/pyomeca/ezc3d/pull/287


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.2...Release_1.5.3

Release_1.5.2
Basically the same, but Python is not left out anymore!

What's Changed
* Re-solves 264 by felixchenier in https://github.com/pyomeca/ezc3d/pull/283
* Made parametrizedWrite available in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/285


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.1...Release_1.5.2

Release_1.5.1
Standardization is good, indeed, but sometimes it can be restrictive. Actually too restrictive. Here at ezc3d we embrace diversity, including c3d diversity. This new release allows for unstandard c3d to be produced so software that requires specific unstandard features to work.
Enjoy diversity!

Release_1.5.0
My name is 3d, ezc3d! That is what you should call me. My CMakeLists as evolved so the way I should be called. You can now called me by my name, and that is it!

This is therefore a much easier way to use ezc3d, but is slightly breaking with previous way to use ezc3d.

What's Changed
* Small Bug Fixes by teliason in https://github.com/pyomeca/ezc3d/pull/250
* bumped to 1.5.0 by pariterre in https://github.com/pyomeca/ezc3d/pull/254

New Contributors
* teliason made their first contribution in https://github.com/pyomeca/ezc3d/pull/250

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.4.10...Release_1.5.0

Release_1.4.9
CMake is a powerful tool, it can help us build - maybe not towers - but great app at least!
But it is also pretty loose in terms of how to use it. Some advance stuff was added so it better uses CMake!
Enjoy CMaking ezc3d!

What's Changed
* CMake improvements by SpaceIm in https://github.com/pyomeca/ezc3d/pull/243
* Fixed the automatic setting of USED when adding new values for rotations by pariterre in https://github.com/pyomeca/ezc3d/pull/246


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.4.8...Release_1.4.9

Release_1.4.10
"I did it Mmyyyyyyyy Waaaaayyyyyyyy" was singing Elvis. As for him, knowing your path is always good. Ezc3d now better knows the path of its file and it can now happily sings that it know "Hiiiiiiiissss Waaaaaayyyyyy"

What's Changed
* CMake improvements by SpaceIm in https://github.com/pyomeca/ezc3d/pull/243
* Fixed the automatic setting of USED when adding new values for rotations by pariterre in https://github.com/pyomeca/ezc3d/pull/246


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.4.8...Release_1.4.10

Release_1.4.8
Everyone loves merry-go-round! Partying while rotating again and again endlessly!
Ezc3d also loves rotating. It actually loves it so much that it decided to implement the ROTATION group introduced by C-Motion.
Will you go round with us?

What's Changed
* Added the capability to ignore bad formatting by pariterre in https://github.com/pyomeca/ezc3d/pull/240
* Added support for Rotation (C++ and Python) by pariterre in https://github.com/pyomeca/ezc3d/pull/241
* Finalized Rotation group by pariterre in https://github.com/pyomeca/ezc3d/pull/242


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.4.7...Release_1.4.8

Release_1.4.7
When your soul disappears, you lose 7 grams so they say. When your marker disappears it looses 16512 [put your preferred units here].
Ezc3d thought it was 1, now it gracefully set it to -16512.
This improves compatibility with MOKKA that requires this very number to mark the marker as missing

What's Changed
* Documentation by pariterre in https://github.com/pyomeca/ezc3d/pull/86
* Added the credential to writter c3d by pariterre in https://github.com/pyomeca/ezc3d/pull/89
* Added the version number of ezc3d in python by pariterre in https://github.com/pyomeca/ezc3d/pull/88
* Added basic BTS c3d and parsing/rebuiding tests by marnunez in https://github.com/pyomeca/ezc3d/pull/90
* Make the tests work again by pariterre in https://github.com/pyomeca/ezc3d/pull/92
* Corrected _version.py folder by pariterre in https://github.com/pyomeca/ezc3d/pull/94
* Version 1.2.2 by pariterre in https://github.com/pyomeca/ezc3d/pull/95
* Add BTS support to the readme by marnunez in https://github.com/pyomeca/ezc3d/pull/96
* Slightly reorganize a CMake and updated version number by pariterre in https://github.com/pyomeca/ezc3d/pull/97
* Change CMAKE_SOURCE_DIR to CMAKE_CURRENT_SOURCE_DIR by lasagnaphil in https://github.com/pyomeca/ezc3d/pull/98
* Get the residuals and the camera masks independently by pariterre in https://github.com/pyomeca/ezc3d/pull/102
* Do not enforce ToUpper anymore for the parameters by pariterre in https://github.com/pyomeca/ezc3d/pull/103
* Version 1.2.3 - ISeeYou by pariterre in https://github.com/pyomeca/ezc3d/pull/104
* Remove the upper() in Python as well by pariterre in https://github.com/pyomeca/ezc3d/pull/105
* Test values by pariterre in https://github.com/pyomeca/ezc3d/pull/107
* Removed mark_as_advanced for the Python3_EXECUTABLE variable so it appears in the GUI by pariterre in https://github.com/pyomeca/ezc3d/pull/110
* Improved the cmake installation of ezc3d by pariterre in https://github.com/pyomeca/ezc3d/pull/112
* Improved the cmake installation of ezc3d by pariterre in https://github.com/pyomeca/ezc3d/pull/113
* Force Platform analysis by pariterre in https://github.com/pyomeca/ezc3d/pull/114
* Export the ezc3d target. by chrisdembia in https://github.com/pyomeca/ezc3d/pull/116
* swig 4.0 instead of 3.0 for travis by pariterre in https://github.com/pyomeca/ezc3d/pull/118
* Release_1.3.0 by pariterre in https://github.com/pyomeca/ezc3d/pull/119
* Added type 4 for force analysis by pariterre in https://github.com/pyomeca/ezc3d/pull/120
* Faster Matrices by pariterre in https://github.com/pyomeca/ezc3d/pull/121
* updated module imports in cmake by pariterre in https://github.com/pyomeca/ezc3d/pull/123
* Updated the matlab binder with the changes of Cmakelist by pariterre in https://github.com/pyomeca/ezc3d/pull/126
* JOSS recommandation on bibtex entry by romainmartinez in https://github.com/pyomeca/ezc3d/pull/127
* Keep literal nan if requested in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/129
* Raising an error message when sending a non string by pariterre in https://github.com/pyomeca/ezc3d/pull/130
* Force platform binders by pariterre in https://github.com/pyomeca/ezc3d/pull/132
* Update __init__.py by aclouthier in https://github.com/pyomeca/ezc3d/pull/134
* Added PYTHON_INSTALL_PREFIX by pariterre in https://github.com/pyomeca/ezc3d/pull/136
* Allow for reading as INT when it is a BYTE by pariterre in https://github.com/pyomeca/ezc3d/pull/139
* Fixed Type 1 and 3 by pariterre in https://github.com/pyomeca/ezc3d/pull/140
* Added tests by pariterre in https://github.com/pyomeca/ezc3d/pull/142
* Converting to Intel float when writing by pariterre in https://github.com/pyomeca/ezc3d/pull/146
* Implemented LABELS2 by pariterre in https://github.com/pyomeca/ezc3d/pull/147
* Force platform Type 1 and 3 by pariterre in https://github.com/pyomeca/ezc3d/pull/141
* Always use fPIC by pariterre in https://github.com/pyomeca/ezc3d/pull/152
* Added the possibility to force cast type when reading a parameter by pariterre in https://github.com/pyomeca/ezc3d/pull/153
* Updated version number by pariterre in https://github.com/pyomeca/ezc3d/pull/154
* Paper for ezc3d by pariterre in https://github.com/pyomeca/ezc3d/pull/156
* Paper first revision by pariterre in https://github.com/pyomeca/ezc3d/pull/157
* Added a warning in the ReadMe and doc for the force platform by pariterre in https://github.com/pyomeca/ezc3d/pull/159
* commentaires francois by fbailly in https://github.com/pyomeca/ezc3d/pull/158
* Paper by pariterre in https://github.com/pyomeca/ezc3d/pull/160
* Fix static windows + hide symbols for GNU compilers by SpaceIm in https://github.com/pyomeca/ezc3d/pull/164
* Allow for include <ezc3d/*.h> by pariterre in https://github.com/pyomeca/ezc3d/pull/166
* Made things easier to create new points in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/171
* Added the capability to remove a parameter and refactor of writing parameters and groups by pariterre in https://github.com/pyomeca/ezc3d/pull/172
* Make offset for ANALOG positive by pariterre in https://github.com/pyomeca/ezc3d/pull/175
* [JOSS REVIEW] Suggestion for paper.md by melund in https://github.com/pyomeca/ezc3d/pull/178
* Add VCPKG section to README.md (fix 161) by RDCH106 in https://github.com/pyomeca/ezc3d/pull/180
* Added the automatic copy of DLL when building for matlab on windows by pariterre in https://github.com/pyomeca/ezc3d/pull/186
* Final paper by pariterre in https://github.com/pyomeca/ezc3d/pull/187
* Added the Statement of need section by pariterre in https://github.com/pyomeca/ezc3d/pull/188
* Added the font to the logo folder by pariterre in https://github.com/pyomeca/ezc3d/pull/189
* Added the font to the logo folder by pariterre in https://github.com/pyomeca/ezc3d/pull/190
* Octave support by pariterre in https://github.com/pyomeca/ezc3d/pull/192
* Added support for motion analysis force platforms by pariterre in https://github.com/pyomeca/ezc3d/pull/196
* Added support for motion analysis force platforms by pariterre in https://github.com/pyomeca/ezc3d/pull/197
* Moved the installation folder of matlab binder so it is set at first config by pariterre in https://github.com/pyomeca/ezc3d/pull/198
* Removed the double free in ezc3d class by pariterre in https://github.com/pyomeca/ezc3d/pull/203
* Documented the shallow copy when copying a c3d structure by pariterre in https://github.com/pyomeca/ezc3d/pull/205
* Delete unnecessary parentheses by Kilidsch in https://github.com/pyomeca/ezc3d/pull/206
* Added event adder by pariterre in https://github.com/pyomeca/ezc3d/pull/207
* Do not add the ANALOG:SCALE if USED is empty (comply with Shogun) by pariterre in https://github.com/pyomeca/ezc3d/pull/210
* Move to AppVeyor by pariterre in https://github.com/pyomeca/ezc3d/pull/214
* Add setup.py by Kilidsch in https://github.com/pyomeca/ezc3d/pull/216
* Speed up writing C3D-files from python by Kilidsch in https://github.com/pyomeca/ezc3d/pull/218
* Added deepcopy for Python by pariterre in https://github.com/pyomeca/ezc3d/pull/222
* Storing missing markers as -16512 by pariterre in https://github.com/pyomeca/ezc3d/pull/228

New Contributors
* marnunez made their first contribution in https://github.com/pyomeca/ezc3d/pull/90
* lasagnaphil made their first contribution in https://github.com/pyomeca/ezc3d/pull/98
* chrisdembia made their first contribution in https://github.com/pyomeca/ezc3d/pull/116
* aclouthier made their first contribution in https://github.com/pyomeca/ezc3d/pull/134
* fbailly made their first contribution in https://github.com/pyomeca/ezc3d/pull/158
* SpaceIm made their first contribution in https://github.com/pyomeca/ezc3d/pull/164
* RDCH106 made their first contribution in https://github.com/pyomeca/ezc3d/pull/180
* Kilidsch made their first contribution in https://github.com/pyomeca/ezc3d/pull/206

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/0.4.0...Release_1.4.7

Release_1.4.6
Have you ever tried to copy yourself? Over and over again? If so, you know everything can't be easily copied... Some choices must be made! Ezc3d python now does this choices for you, allowing for deepcopy itself!

Create more and more c3d, more than ever!

Release_1.4.5
Vicon Shogun did not like C3D from ezc3d. We talk to each others, found common ground. Now they love each other
Long live to the Shogun/ezc3d relationship!

Release_1.4.4
The biggest event you can imagine is of course a surprise party! But ezc3d was not allowing you to organize one... That is no longer the case! By adding an event in the c3d, you can add an fun (and less fun) event!

Release_1.4.3
Motion Analyses uses its own way to store the calibration Matrix. Unfortunately, ezc3d was unaware of it... This is now something from the past and ezc3d now knows how to deal with such C3D files :)

Release_1.4.2
As in the Zeno's paradox, you think you are almost there, but never quite!

Release_1.4.1
Zenodo is a bit picky.. It really wants to be there when you release! Here is a rerelease of 1.4.0 :)

Release_1.4.0
So much work, but ezc3d finally got there, it is now publish! This release is the actual version of the publication
Thanks everyone for your support!

Release_1.3.9
For some reason, people doesn't agree on positive and negative direction sometimes. EZC3D was therefore confuse... But now, it makes a much better job for the sign convention when reading analog data!

Release_1.3.8
For some reason ezc3d was really bonded to its parameters. It didn't want to let it go!
Now ezc3d has gain in self confidence and allows for parameters deletion.

Also, ezc3d is more verbose on some errors :)

Release_1.3.7
Perfection! Oh dear perfection! We all want it... but at the same time it is so far. So far away that it makes us forget that the reason we do things is not so everything is in place and well organize, but to do actual work!

Ezc3d get a bit looser, it now accept that, MAYBE! you don't know the type of your parameters... So it will convert them to another format if you ask so. More specifically, Int and Double parameters can be casted as you wish. But use this power wisely!

Release_1.3.6
Covid19 thought us something important, we human love to aggregate! This is especially true when you have skin markers on you. Sadly EZC3D was limiting you to 255 skin markers.

But this is no longer true. Now, using the new tag LABELS2 (and 3 or 4!) you can define as much marker friends as you want! This even works for the Analog data as well.

So let's virtually party up (this is still lock down, after all...)

Release_1.3.5
Force platform filter was only for C++, but MATLAB and Python were sad because of this. But having your programming languages sad at you is not a good thing. So we made them happy by providing them more code!

Release_1.3.4
ezc3d/matlab was pretty sensitive on what you were saying to him. I mean, if you were to send him a string but decided not too, she would get angry with you, and simply close Matlab! Now, she still get angry, but at least, she tells you that you should have communicated better.

Release_1.5.17
Ezc3d was walking down the street, abandoned by the "ez" part of its name. Sad and lonely, he was thinking... How can I be made ez again. And the light came on the form of four letters PyPI. Ezc3d worked hard, and now he is accepted on PyPI!! HipPyPI Hurray for ezc3d!

What's Changed
* Update README.md by SjoerdBruijn in https://github.com/pyomeca/ezc3d/pull/340
* Update README.md by mrrezaie in https://github.com/pyomeca/ezc3d/pull/344
* Finalized PyPI by pariterre in https://github.com/pyomeca/ezc3d/pull/348

New Contributors
* SjoerdBruijn made their first contribution in https://github.com/pyomeca/ezc3d/pull/340
* mrrezaie made their first contribution in https://github.com/pyomeca/ezc3d/pull/344

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.11...Release_1.5.17

Release_1.5.11
Matlab users behold! Your time of easyness has finally come! After all these years of being left behind by us, you finally can enjoy ezc3d without the struggle to install ezc3d by yourself, as the binaries are now provided! Friends, enjoy!

What's Changed
* Added an example how to modifiy a file in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/324
* Fixed regex for python setup install by pariterre in https://github.com/pyomeca/ezc3d/pull/329
* Fixed subframes inversion in rotation for python by pariterre in https://github.com/pyomeca/ezc3d/pull/330
* Added support for arm64 on macos for the matlab binding by pariterre in https://github.com/pyomeca/ezc3d/pull/333
* Push matlab binaries github action by pariterre in https://github.com/pyomeca/ezc3d/pull/335
* Removed useless multiple matlab compilation by pariterre in https://github.com/pyomeca/ezc3d/pull/336
* Video for Matlab binaries by Ipuch in https://github.com/pyomeca/ezc3d/pull/337


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.10...Release_1.5.11

Release_1.5.10
Something when things go south, we need to express ourselves. Ezc3d was struggling telling what was bothering it properly! Thanks this release some errors are now easier to understand

What's Changed
* Fixed computation of number of frames of Rotations in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/317
* Improved some error messages by pariterre in https://github.com/pyomeca/ezc3d/pull/322


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.9...Release_1.5.10

Release_1.5.9
When people leave, they want to be remembered as much as they can. Unlike people though, data are expected to forgotten when they leave. But Python was holding hard to that data. We thought Python to let it go.... and fixed the memory leak!

What's Changed
* Fixed memory leak when using to_array() in python by pariterre in https://github.com/pyomeca/ezc3d/pull/315


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.8...Release_1.5.9

Release_1.5.8
Once in a while, a shady company implements their version of ezc3d. Quite often, this comes with caveat as they don't fully comply to what one would call "standard". Still, ezc3d enjoys welcoming new comers! That is why, we are now embracing the Shadow implementation.
Long live to this new friendship!

What's Changed
* Made the SHADOW company sloppy implemented readable by pariterre in https://github.com/pyomeca/ezc3d/pull/309
* Disregarded the first two bytes of parameters section when reading by pariterre in https://github.com/pyomeca/ezc3d/pull/310
* Made FPCOPPOLY optional for type-3 force platforms by pariterre in https://github.com/pyomeca/ezc3d/pull/311


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.7...Release_1.5.8

Release_1.5.7
When you have something to do, you can be careful and checking again and again and again, making sure no mistake is made. But at some point, when you know things are good, as everyone know: just do it! Ezc3d can now add frames in batch so they are not verified individually but only once drastically increasing the spead of creating large files.

What's Changed
* Fixed Python from the previous update by pariterre in https://github.com/pyomeca/ezc3d/pull/304
* Fixed number of frames for nframes > 32767 and made creating them much faster by pariterre in https://github.com/pyomeca/ezc3d/pull/305


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.6...Release_1.5.7

Release_1.5.6
During is infamous discussion, Councillor Hamann says a that the one has a good point. Here in ezc3d, we always try to make good points. However, some company prefers not. As Kistler failed to have good points in their c3d, ezc3d must now make it for them!

What's Changed
* add units in Points to make it readable by mokka by Ipuch in https://github.com/pyomeca/ezc3d/pull/299
* Added capability to read Kistler's c3d files by pariterre in https://github.com/pyomeca/ezc3d/pull/302

New Contributors
* Ipuch made their first contribution in https://github.com/pyomeca/ezc3d/pull/299

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.5...Release_1.5.6

Release_1.5.5
There was a time where everything was easy, one could get water at the river and drink. Nowadays, everything is more complex. A good example is to compute the center of pressure. It could be as easy as computing it, but Kistler made it slightly more sophisticated. Ezc3d adores what is sophisticated and had a desire to compute it properly. It is now done!

What's Changed
* Typo by pariterre in https://github.com/pyomeca/ezc3d/pull/298
* Added Kistler FPCOPPOLY tag by pariterre in https://github.com/pyomeca/ezc3d/pull/297


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.4...Release_1.5.5

Release_1.5.4
With the rotation built-in, ezc3d was WAYYYYY to happy to have them in Matlab and would go crazy creating A LOOOOT of them. We had to restrict its enthousiasm.

Limitation tastes better!

What's Changed
* [RTM] MATLAB explanations by EveCharbie in https://github.com/pyomeca/ezc3d/pull/288

New Contributors
* EveCharbie made their first contribution in https://github.com/pyomeca/ezc3d/pull/288

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.3...Release_1.5.4

Release_1.5.3
Matlab is a well-known software to deal with matrices, it is basically in its name (MATrix LABoratory)!
Still, ezc3d was ignoring that fact and did not allowed to access Rotations feature on Matlab. It is now fully fixed and Matlab can be as happy as Python!

What's Changed
* Added support for files with Rotations in Matlab by pariterre in https://github.com/pyomeca/ezc3d/pull/287


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.2...Release_1.5.3

Release_1.5.2
Basically the same, but Python is not left out anymore!

What's Changed
* Re-solves 264 by felixchenier in https://github.com/pyomeca/ezc3d/pull/283
* Made parametrizedWrite available in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/285


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.5.1...Release_1.5.2

Release_1.5.1
Standardization is good, indeed, but sometimes it can be restrictive. Actually too restrictive. Here at ezc3d we embrace diversity, including c3d diversity. This new release allows for unstandard c3d to be produced so software that requires specific unstandard features to work.
Enjoy diversity!

Release_1.5.0
My name is 3d, ezc3d! That is what you should call me. My CMakeLists as evolved so the way I should be called. You can now called me by my name, and that is it!

This is therefore a much easier way to use ezc3d, but is slightly breaking with previous way to use ezc3d.

What's Changed
* Small Bug Fixes by teliason in https://github.com/pyomeca/ezc3d/pull/250
* bumped to 1.5.0 by pariterre in https://github.com/pyomeca/ezc3d/pull/254

New Contributors
* teliason made their first contribution in https://github.com/pyomeca/ezc3d/pull/250

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.4.10...Release_1.5.0

Release_1.4.9
CMake is a powerful tool, it can help us build - maybe not towers - but great app at least!
But it is also pretty loose in terms of how to use it. Some advance stuff was added so it better uses CMake!
Enjoy CMaking ezc3d!

What's Changed
* CMake improvements by SpaceIm in https://github.com/pyomeca/ezc3d/pull/243
* Fixed the automatic setting of USED when adding new values for rotations by pariterre in https://github.com/pyomeca/ezc3d/pull/246


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.4.8...Release_1.4.9

Release_1.4.10
"I did it Mmyyyyyyyy Waaaaayyyyyyyy" was singing Elvis. As for him, knowing your path is always good. Ezc3d now better knows the path of its file and it can now happily sings that it know "Hiiiiiiiissss Waaaaaayyyyyy"

What's Changed
* CMake improvements by SpaceIm in https://github.com/pyomeca/ezc3d/pull/243
* Fixed the automatic setting of USED when adding new values for rotations by pariterre in https://github.com/pyomeca/ezc3d/pull/246


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.4.8...Release_1.4.10

Release_1.4.8
Everyone loves merry-go-round! Partying while rotating again and again endlessly!
Ezc3d also loves rotating. It actually loves it so much that it decided to implement the ROTATION group introduced by C-Motion.
Will you go round with us?

What's Changed
* Added the capability to ignore bad formatting by pariterre in https://github.com/pyomeca/ezc3d/pull/240
* Added support for Rotation (C++ and Python) by pariterre in https://github.com/pyomeca/ezc3d/pull/241
* Finalized Rotation group by pariterre in https://github.com/pyomeca/ezc3d/pull/242


**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/Release_1.4.7...Release_1.4.8

Release_1.4.7
When your soul disappears, you lose 7 grams so they say. When your marker disappears it looses 16512 [put your preferred units here].
Ezc3d thought it was 1, now it gracefully set it to -16512.
This improves compatibility with MOKKA that requires this very number to mark the marker as missing

What's Changed
* Documentation by pariterre in https://github.com/pyomeca/ezc3d/pull/86
* Added the credential to writter c3d by pariterre in https://github.com/pyomeca/ezc3d/pull/89
* Added the version number of ezc3d in python by pariterre in https://github.com/pyomeca/ezc3d/pull/88
* Added basic BTS c3d and parsing/rebuiding tests by marnunez in https://github.com/pyomeca/ezc3d/pull/90
* Make the tests work again by pariterre in https://github.com/pyomeca/ezc3d/pull/92
* Corrected _version.py folder by pariterre in https://github.com/pyomeca/ezc3d/pull/94
* Version 1.2.2 by pariterre in https://github.com/pyomeca/ezc3d/pull/95
* Add BTS support to the readme by marnunez in https://github.com/pyomeca/ezc3d/pull/96
* Slightly reorganize a CMake and updated version number by pariterre in https://github.com/pyomeca/ezc3d/pull/97
* Change CMAKE_SOURCE_DIR to CMAKE_CURRENT_SOURCE_DIR by lasagnaphil in https://github.com/pyomeca/ezc3d/pull/98
* Get the residuals and the camera masks independently by pariterre in https://github.com/pyomeca/ezc3d/pull/102
* Do not enforce ToUpper anymore for the parameters by pariterre in https://github.com/pyomeca/ezc3d/pull/103
* Version 1.2.3 - ISeeYou by pariterre in https://github.com/pyomeca/ezc3d/pull/104
* Remove the upper() in Python as well by pariterre in https://github.com/pyomeca/ezc3d/pull/105
* Test values by pariterre in https://github.com/pyomeca/ezc3d/pull/107
* Removed mark_as_advanced for the Python3_EXECUTABLE variable so it appears in the GUI by pariterre in https://github.com/pyomeca/ezc3d/pull/110
* Improved the cmake installation of ezc3d by pariterre in https://github.com/pyomeca/ezc3d/pull/112
* Improved the cmake installation of ezc3d by pariterre in https://github.com/pyomeca/ezc3d/pull/113
* Force Platform analysis by pariterre in https://github.com/pyomeca/ezc3d/pull/114
* Export the ezc3d target. by chrisdembia in https://github.com/pyomeca/ezc3d/pull/116
* swig 4.0 instead of 3.0 for travis by pariterre in https://github.com/pyomeca/ezc3d/pull/118
* Release_1.3.0 by pariterre in https://github.com/pyomeca/ezc3d/pull/119
* Added type 4 for force analysis by pariterre in https://github.com/pyomeca/ezc3d/pull/120
* Faster Matrices by pariterre in https://github.com/pyomeca/ezc3d/pull/121
* updated module imports in cmake by pariterre in https://github.com/pyomeca/ezc3d/pull/123
* Updated the matlab binder with the changes of Cmakelist by pariterre in https://github.com/pyomeca/ezc3d/pull/126
* JOSS recommandation on bibtex entry by romainmartinez in https://github.com/pyomeca/ezc3d/pull/127
* Keep literal nan if requested in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/129
* Raising an error message when sending a non string by pariterre in https://github.com/pyomeca/ezc3d/pull/130
* Force platform binders by pariterre in https://github.com/pyomeca/ezc3d/pull/132
* Update __init__.py by aclouthier in https://github.com/pyomeca/ezc3d/pull/134
* Added PYTHON_INSTALL_PREFIX by pariterre in https://github.com/pyomeca/ezc3d/pull/136
* Allow for reading as INT when it is a BYTE by pariterre in https://github.com/pyomeca/ezc3d/pull/139
* Fixed Type 1 and 3 by pariterre in https://github.com/pyomeca/ezc3d/pull/140
* Added tests by pariterre in https://github.com/pyomeca/ezc3d/pull/142
* Converting to Intel float when writing by pariterre in https://github.com/pyomeca/ezc3d/pull/146
* Implemented LABELS2 by pariterre in https://github.com/pyomeca/ezc3d/pull/147
* Force platform Type 1 and 3 by pariterre in https://github.com/pyomeca/ezc3d/pull/141
* Always use fPIC by pariterre in https://github.com/pyomeca/ezc3d/pull/152
* Added the possibility to force cast type when reading a parameter by pariterre in https://github.com/pyomeca/ezc3d/pull/153
* Updated version number by pariterre in https://github.com/pyomeca/ezc3d/pull/154
* Paper for ezc3d by pariterre in https://github.com/pyomeca/ezc3d/pull/156
* Paper first revision by pariterre in https://github.com/pyomeca/ezc3d/pull/157
* Added a warning in the ReadMe and doc for the force platform by pariterre in https://github.com/pyomeca/ezc3d/pull/159
* commentaires francois by fbailly in https://github.com/pyomeca/ezc3d/pull/158
* Paper by pariterre in https://github.com/pyomeca/ezc3d/pull/160
* Fix static windows + hide symbols for GNU compilers by SpaceIm in https://github.com/pyomeca/ezc3d/pull/164
* Allow for include <ezc3d/*.h> by pariterre in https://github.com/pyomeca/ezc3d/pull/166
* Made things easier to create new points in Python by pariterre in https://github.com/pyomeca/ezc3d/pull/171
* Added the capability to remove a parameter and refactor of writing parameters and groups by pariterre in https://github.com/pyomeca/ezc3d/pull/172
* Make offset for ANALOG positive by pariterre in https://github.com/pyomeca/ezc3d/pull/175
* [JOSS REVIEW] Suggestion for paper.md by melund in https://github.com/pyomeca/ezc3d/pull/178
* Add VCPKG section to README.md (fix 161) by RDCH106 in https://github.com/pyomeca/ezc3d/pull/180
* Added the automatic copy of DLL when building for matlab on windows by pariterre in https://github.com/pyomeca/ezc3d/pull/186
* Final paper by pariterre in https://github.com/pyomeca/ezc3d/pull/187
* Added the Statement of need section by pariterre in https://github.com/pyomeca/ezc3d/pull/188
* Added the font to the logo folder by pariterre in https://github.com/pyomeca/ezc3d/pull/189
* Added the font to the logo folder by pariterre in https://github.com/pyomeca/ezc3d/pull/190
* Octave support by pariterre in https://github.com/pyomeca/ezc3d/pull/192
* Added support for motion analysis force platforms by pariterre in https://github.com/pyomeca/ezc3d/pull/196
* Added support for motion analysis force platforms by pariterre in https://github.com/pyomeca/ezc3d/pull/197
* Moved the installation folder of matlab binder so it is set at first config by pariterre in https://github.com/pyomeca/ezc3d/pull/198
* Removed the double free in ezc3d class by pariterre in https://github.com/pyomeca/ezc3d/pull/203
* Documented the shallow copy when copying a c3d structure by pariterre in https://github.com/pyomeca/ezc3d/pull/205
* Delete unnecessary parentheses by Kilidsch in https://github.com/pyomeca/ezc3d/pull/206
* Added event adder by pariterre in https://github.com/pyomeca/ezc3d/pull/207
* Do not add the ANALOG:SCALE if USED is empty (comply with Shogun) by pariterre in https://github.com/pyomeca/ezc3d/pull/210
* Move to AppVeyor by pariterre in https://github.com/pyomeca/ezc3d/pull/214
* Add setup.py by Kilidsch in https://github.com/pyomeca/ezc3d/pull/216
* Speed up writing C3D-files from python by Kilidsch in https://github.com/pyomeca/ezc3d/pull/218
* Added deepcopy for Python by pariterre in https://github.com/pyomeca/ezc3d/pull/222
* Storing missing markers as -16512 by pariterre in https://github.com/pyomeca/ezc3d/pull/228

New Contributors
* marnunez made their first contribution in https://github.com/pyomeca/ezc3d/pull/90
* lasagnaphil made their first contribution in https://github.com/pyomeca/ezc3d/pull/98
* chrisdembia made their first contribution in https://github.com/pyomeca/ezc3d/pull/116
* aclouthier made their first contribution in https://github.com/pyomeca/ezc3d/pull/134
* fbailly made their first contribution in https://github.com/pyomeca/ezc3d/pull/158
* SpaceIm made their first contribution in https://github.com/pyomeca/ezc3d/pull/164
* RDCH106 made their first contribution in https://github.com/pyomeca/ezc3d/pull/180
* Kilidsch made their first contribution in https://github.com/pyomeca/ezc3d/pull/206

**Full Changelog**: https://github.com/pyomeca/ezc3d/compare/0.4.0...Release_1.4.7

Release_1.4.6
Have you ever tried to copy yourself? Over and over again? If so, you know everything can't be easily copied... Some choices must be made! Ezc3d python now does this choices for you, allowing for deepcopy itself!

Create more and more c3d, more than ever!

Release_1.4.5
Vicon Shogun did not like C3D from ezc3d. We talk to each others, found common ground. Now they love each other
Long live to the Shogun/ezc3d relationship!

Release_1.4.4
The biggest event you can imagine is of course a surprise party! But ezc3d was not allowing you to organize one... That is no longer the case! By adding an event in the c3d, you can add an fun (and less fun) event!

Release_1.4.3
Motion Analyses uses its own way to store the calibration Matrix. Unfortunately, ezc3d was unaware of it... This is now something from the past and ezc3d now knows how to deal with such C3D files :)

Release_1.4.2
As in the Zeno's paradox, you think you are almost there, but never quite!

Release_1.4.1
Zenodo is a bit picky.. It really wants to be there when you release! Here is a rerelease of 1.4.0 :)

Release_1.4.0
So much work, but ezc3d finally got there, it is now publish! This release is the actual version of the publication
Thanks everyone for your support!

Release_1.3.9
For some reason, people doesn't agree on positive and negative direction sometimes. EZC3D was therefore confuse... But now, it makes a much better job for the sign convention when reading analog data!

Release_1.3.8
For some reason ezc3d was really bonded to its parameters. It didn't want to let it go!
Now ezc3d has gain in self confidence and allows for parameters deletion.

Also, ezc3d is more verbose on some errors :)

Release_1.3.7
Perfection! Oh dear perfection! We all want it... but at the same time it is so far. So far away that it makes us forget that the reason we do things is not so everything is in place and well organize, but to do actual work!

Ezc3d get a bit looser, it now accept that, MAYBE! you don't know the type of your parameters... So it will convert them to another format if you ask so. More specifically, Int and Double parameters can be casted as you wish. But use this power wisely!

Release_1.3.6
Covid19 thought us something important, we human love to aggregate! This is especially true when you have skin markers on you. Sadly EZC3D was limiting you to 255 skin markers.

But this is no longer true. Now, using the new tag LABELS2 (and 3 or 4!) you can define as much marker friends as you want! This even works for the Analog data as well.

So let's virtually party up (this is still lock down, after all...)

Release_1.3.5
Force platform filter was only for C++, but MATLAB and Python were sad because of this. But having your programming languages sad at you is not a good thing. So we made them happy by providing them more code!

Release_1.3.4
ezc3d/matlab was pretty sensitive on what you were saying to him. I mean, if you were to send him a string but decided not too, she would get angry with you, and simply close Matlab! Now, she still get angry, but at least, she tells you that you should have communicated better.

Release_1.3.3
Despite being awesome, `ezc3d` is not alone in the world! And c3d should be the same no matter who is reading it. However, when using Python, the c3d created was storing nan as zeros. `ezc3d` knew that, but the others did not.

Not `ezc3d` puts the nan directly in the file, so you can see (or not see) those nan in other software!

Release_1.3.2
The custom linear algebra library was a bit to slow when allocating known sized matrices. Ezc3d was angry! So the linear algebra library improved :D It is now a bit faster!

Release_1.3.1
The ADN of biomechanical data is composed of Points and Force data. But if you are limited to one type of data, you are pretty narrow in the grand scheme of the biomechanics.

The new Force platform filter of EZC3D opens and is now available for more Platform type, that is the Type 4!

Enjoy C3Dying with us :)

Release_1.3.0
It is important to know your forces and weaknesses. EZC3D doesn't make exception!
So now, if you have force platforms in your C3D, you can ask for a Force plateform analysis that will tell you everything you need to know about these force plate (forces, moments, center of pressure, etc.)

This release is the first commit which was used by OpenSim as a backend reader for C3D :D

Release_1.2.4
Trusting blindly your skills is a leap of faith. Don't get me wrong, this is good! But sometimes having a tool that tells you where you stands is useful.

EZC3D now gives you a hand when it comes to understanding what happens to your marker. The cameras that sees the markers are now available to the user, as well as the quality of the reconstruction! We hope you will c3 even better now!


Release_1.2.3
Trusting blindly your skills is a leap of faith. Don't get me wrong, this is good! But sometimes having a tool that tells you where you stands is useful.

EZC3D now gives you a hand when it comes to understanding what happens to your marker. The cameras that sees the markers are now available to the user, as well as the quality of the reconstruction! We hope you will c3 even better now!

Release_1.2.2
Doing great things alone is great, but doing great thing together is fulfilling!

EZC3D have had some external help which was highly appreciated. Thanks to this, a lot of small bugs were fixed and Mokka was never so well supported. Some convention used in most C3D was also added when writing a new one. Moreover, the BTS implementation of C3D is also supported.

All these makes C3Ding even better! Why don't you try :)


Release_1.2.1
Doing great things alone is great, but doing great thing together is fulfilling!

EZC3D have had some external help which was highly appreciated. Thanks to this, a lot of small bugs were fixed and Mokka was never so well supported. Some convention used in most C3D was also added when writing a new one. Moreover, the BTS implementation of C3D is also supported.

All these makes C3Ding even better! Why don't you try :)

Release_1.2.0
For some reason EZC3D was sometime a lot confused by the way C3D were written. Because of that, in some specific condition, EZC3D was swapping parameters which is indeed stupid stuff!

EZC3D doesn't get confused anymore while random C3D files are read!

NB: This is a major bug fix and one should not use the release before that point because there is no prior way to know if the C3D will or will not get mixed up!

Release_1.1.1
*ezc3d* is really sensitive. A little nothing gives it so much emotion!
Today *ezc3d* dives head first into its sensitivity by adding XSens to its supported companies. Enjoy full XSensing your c3d files!

Release_1.1.0
You remember these good old days that everyone forget? Not ezc3d! Ezc3d remembers. It remembers that someday, not so far away that storing floating point was taking to much of the precious disk space. It remembers that Intel was not the sole producer of computer chip. It remembers, and it felt nostalgic!

We gave the oportunity to ezc3d to interact will this past that sometime strikes back! Ezc3d can now reads Integer formated files. It also can read formating from DEC storage float points.

With this release, people from now and then can c3dying in peace!

Release_1.0.1
What is best than having a good coffee while c3dying data? Having a moka of course!
Mokka is now happy with c3d from ezc3d. Actually all software should be happy to work hand in hand with ezc3d.
Still, having a good moka is always nice!

Release_1.0.0
What is best than having a good coffee while c3dying data? Having a moka of course!
Mokka is now happy with c3d from ezc3d. Actually all software should be happy to work hand in hand with ezc3d.
Still, having a good moka is always nice!

Release_0.4.0
EZC3D is now able to eat HUGE C3D files (tested up to 700 Mo). Doing so, it lost some of its memory... The points and analog channels are no longer able to be aware of their names (Warning, this can break some codes...). However, the structure for point and analog labels has been highly simplified.

So even if EZC3D doesn't always remember who it is, it is still as eager to play with data.

Release_0.3.6
Some legacy code from the past has been removed due to new features and new orientation of the library.

Ezc3d also no longer consider the initial structure when it reads a c3d (leading to some rearrangement in the parameter section). Do so, it insures that the c3d which is write back afterwards is an actual valid structure.

Don't look back, look for the future!

Release_0.3.5
Ezc3d gets in maturity! It is now able to read very large files on Mac, Windows and Linux!

Enjoy, ezeying large c3d :)

Release_0.3.4