Hi, Jason, On Jan 24, 2013, at 4:41 AM, Jason Manley wrote:
> I think tagged releases of the git libraries for given versions are > appropriate. But it's certainly our intent that the SKA-SA repo will always > reflect our latest developments, including support for the latest tools > whenever possible. That's fine for you and others who like updating their tools several times a year, but requiring folks to update their tools just to get a bug fix to the library seems kind of harsh. For example, the current HEAD commit on the ska-sa mlib_devel github repo (e0110e5) fixes support for ROACH DRAM, but two of the library model files were updated using a new version of Simulink (8.0 it looks like) that saves mask information in a way that is not compatible with earlier versions. People (like me) who don't use this new Simulink version but (try to) update to your latest and greatest will find that some of the CASPER blocks (e.g. the snapshot block) no longer have masks! At the very least, it would be nice to have a model callback that would open an error dialog if the user is not using a new enough version of Simulink. Matlab does display a warning message, but given the drastic difference in how the new Simulink version handles masks I think it should be a hard-to-ignore error. Dave P.S. Detailed commit logs about mdl file changes would make it easier for others to back port the fix since mdl files cannot be diff-ed in a useful way. :-)
