Recently the BNL Wire-Cell group had a discussion on WCT's architecture and design. The slides may be interesting to others.
Updates from the Wire-Cell team.
Releases 0.15, 0.16 and 0.17 (in prep) come with some changes worth mentioning. So, here we mention them. At length….
Some changes are "breaking" and others provide new, better ways to do things. Many are cleanups which were needed for a while. As 0.17 is not technically cut, it may have additional changes. So, sit back and read about some of the improvements that you may not yet have learned about.
As Wire-Cell Toolkit is a toolkit, it does not force a top-down
structure starting from a
main() function. But, it does provide a
layered top-down structure that applications may use after taking
their own choice of entry point. This post talks about a layer of
this structure called a WCT "app".
Of course, everyone is a fan of Wire-Cell. This post isn't about you. It's about a common pattern that is found in Wire-Cell data flow graphs and how this pattern is realized at the WCT C++ level and how to form it in WCT configuration.
The Waf-based build system for the toolkit is recently cleaned up and expanded to support user packages. For existing users this change should be invisible. This post gives the details of the change, what to do when updates to the build system are needed and how to use it for to build your own WCT-related packages.
Wire-Cell and Bee have logos!
Previously posts have discussed Singularity containers which were introduced to provide easy development environments. Recently, Docker container descriptions have been developed to introduce Travis-CI continuous integration to the Wire-Cell Toolkit.
A new Singularity container is available which provides Kerberos clients, kx509 and other stuff that is needed to download DUNE data.