On Monday, June 6, 2016 at 8:07:22 AM UTC, Islam Badreldin wrote: > > Hi, > > I'm excited to announce the first release of POSIXClock, a package that > provides Julia bindings to clock_*() functions from POSIX real-time > extensions (librt on Linux). > https://github.com/ibadr/POSIXClock.jl >
Accurate clock might be of interest to not only real-time computing? [Unclear to me if librt/clock_*() works without PREEMPT_RT patch.] And of interest to e.g. the real-time satellite telescope in Julia.. see link below: > > Special care was devoted to completely avoiding memory allocations in the > real-time section of the code by using in-place operations and > pre-allocating all the needed variables, as well as by disabling the > garbage collector. > I'm not convinced disabling the GC is needed [or even helpful when there are allocations, see my rambling at link below and comments from others and pointers to Julia issues.] > > This package should appeal to roboticists interested in Julia (I have > successfully tested this package with blinking a GPIO on the BeagleBone > Black using the mraa library), as well as to scientists conducting > closed-loop experiments with soft or hard real-time requirements. (Hard > real-time performance requires a recent Linux kernel with the PREEMPT_RT > patch.) > Note in the link below, a link to Linus Torvalds on real-time Linux. Caches are a problem. Be careful, even with this patch.. > > In addition to this announcement, I have a couple of questions pertaining > to best practices for writing real-time Julia code and avoiding memory > allocations, as well as to sharing arrays between two Julia instances (one > is real-time and the other is regular). Is it best to post these questions > in this thread, or to create a new thread for these questions? > Feel free to look at this recent link on [soft, hard?] real-time and add questions there (since it's for a specific project, you may want to start a new thread): https://groups.google.com/forum/#!topic/julia-users/qgnNbbuwMIY [If you add to that thread, you could point there to this thread.] -- Palli.
