Less than two months since our previous release, we are very proud to announce the release of version 1.3.1 of Luminescence. This is a minor release that brings a few regression fixes and a number of cosmetic improvements, alongside increased robustness and correctness.

For a change of pace, it’s nice, every now and then, to have a release that doesn’t try to do too much or that brings breaking changes. Given the summer time and the slightly delayed release of 1.3.0, this release cycle has been short and sweet. Despite all that, in total we addressed 55 issues in 174 commits.

Just over seven months since our previous release of RLumShiny, we are pleased to announce the release of RLumShiny 0.2.8. In the past months we’ve been chipping away at fixing little bugs and annoyances, as well as keeping compatibility with the recent Luminescence 1.3.0.

While there are no new apps in this version, during we have strengthened and improved a good number of the existing ones, especially those that were added the last time round.

Big thanks, as always, to Christoph Burow for handling the actual release and publishing the package on CRAN.

We are very excited to announce the release of version 1.3.0 of the Luminescence R package. This is a major release that comes after 4 months since our previous release.

This release brings a number of changes and improvements under the hood, which may unfortunately cause deprecation warnings to appear in your scripts. There are also a number of small fixes to the plotting functions and an exciting new function. In total we addressed 47 issues in 261 commits.

Today I am presenting the CBTF (Caught by the Fuzz!) package at the useR! 2026 conference in Warsaw.

I have already written about CBTF in the past. The package has grown a lot in the meantime, adding new functionality, better user experience and lighting-fast performance.

Only two weeks after our previous release, we are proud to announce the release of version 1.2.1 of the Luminescence R package. This is a minor release made upon request by CRAN, as we’ll explain further down. Nonetheless, there are a few interesting changes and some regression fixes (mainly cosmetic) that make it worthwhile to update. In total we solved 25 issues in 60 commits.

We are very excited to announce the release of version 1.2.0 of the Luminescence R package. This is a major release that, once again, comes exactly 3 months after our previous release.

There are a lot of exciting things to discuss about this release, many of which related to consistency in function argument names and behaviour, but also new functionalities and some quality of life improvements. In total we solved 112 issues in 415 commits.

From 4 to 6 March 2026, the REPLAY project team convened for its second annual meeting at Schloss Rauischholzhausen, a historic 19th-century hunting lodge near Giessen.

It has been a while since our previous update concerning RLumShiny. However, work on that front has continued and in the last month we had not only one but two releases (more on that below).

The work leading to the RLumShiny 0.2.7 release concentrated on adding three new apps and improving the internal infrastructure to import more file types.

The next release of Luminescence (which we expect in March) will bring some small but potentially breaking changes to users. This post is meant to give some advance warnings and provide solutions so that updating the package version will not cause excessive pain.

Another 3 months exact from our previous release, we are very proud to announce the release of version 1.1.2 of the Luminescence R package.

This release comes with a many (mostly rare) crashes being fixed, a number of cosmetic improvements to the plots, and a massive speed boost in the analyse_IRSAR.RF() function. Behind the scenes, during these past months we have introduced some improvements to our test infrastructure and continued our process of deprecation of redundant functions. In total we addressed 109 issues in 523 commits.