The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

mctq 0.3.2 (2023-02-19)

mctq 0.3.1 (2022-11-03)

mctq 0.3.0 (2022-08-20)

mctq 0.2.0 (2022-05-08)

mctq 0.1.0 (2021-11-04)

mctq 0.0.0.9002 (prerelease)

mctq 0.0.0.9001 (prerelease)

Breaking changes

New features

Minor improvements and fixes

Note about removing convert()

convert() was created considering the user experience (sleep and chronobiology scientists). Since most of them don’t have much experience with R and that time can have different types of representations (e.g., decimal hours, radian), convert() aim was to help transpose those difficulties, posing as an “universal translator” (🖖).

However, after much thought and consideration, we believe that the convert() feature may be out of the mctq scope. It can maybe be part of another package (a lubritime package perhaps? 😄). Other mctq tools, like shorter_interval() and sum_time(), could also be a part of that package (but are necessary in mctq for the time being). Hence, we decided to remove convert() and to instruct the user to check the lubridate and hms packages for parsing/conversion.

Note about renaming sd() and ms()

That was a tough, but necessary, call. Although we tried to preserve the original author’s naming pattern for the MCTQ functions, the name sd provokes a dangerous name collision with the widely used stats::sd() function (standard deviation) and the name ms provokes a name collision with lubridate::ms() (a function for parsing minutes and seconds components). That’s why we decided to renamed them. sdu() and msl() are the only exceptions, all the other mctq functions maintain a strong naming resemblance with the original author’s naming pattern.

mctq 0.0.0.9000 (prerelease)

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.