{"id":7769,"date":"2016-08-12T09:00:00","date_gmt":"2016-08-12T13:00:00","guid":{"rendered":"https:\/\/blogs.mathworks.com\/pick\/?p=7769"},"modified":"2019-04-03T14:22:28","modified_gmt":"2019-04-03T18:22:28","slug":"chebfun-current-version","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/pick\/2016\/08\/12\/chebfun-current-version\/","title":{"rendered":"Chebfun – Current Version"},"content":{"rendered":"
\r\n \r\n

Sean<\/a>'s pick this week is Chebfun - Current Version<\/a> by the Chebfun Team<\/a>.\r\n <\/p>\r\n <\/introduction>\r\n\r\n

My pick this week is the current version of Chebfun. Some of you may be thinking: \"You're repicking it, it's already been picked<\/a>\" and discussed on Cleve's blog<\/a>! This is sort of true; the previous version of chebfun was picked and is still available.\r\n <\/p>\r\n

But I'm not going to spend my time trying to show you great examples or talk about the usefulness of this tool. The chebfun\r\n team already has a great example gallery<\/a>, which is very similar to the MathWorks example gallery<\/a>, that covers the vast range of capabilities.\r\n <\/p>\r\n

I'm going to discuss the conversation I had with Professor Trefethen<\/a>, the inventor of Chebfun, at the annual SIAM conference in July, 2016. He approached me at the MathWorks booth and wanted\r\n to know why the older version continues to see so many downloads when they're trying to encourage users to migrate to the\r\n new one? Here's a screenshot of the current downloads:\r\n <\/p>\r\n

<\/p>\r\n

As you can see over the last 30 days (August 9, 2016), the old version has 41 downloads compared to 68 for the new one. But\r\n it clearly says \"Please download current version\". The description on the file's page repeats this and points at the new\r\n one and the chebfun website. Professor Trefethen was curious what could be done to migrate more people to the current version.\r\n The challenge is that he'd like the older version to remain available for people who intentionally need backward compatibility\r\n but not for any new users.\r\n <\/p>\r\n

I suggested that the older code and example files be removed from the File Exchange and replaced with a readme that points\r\n to the current version. After some explaining the enhancements and fair warning, the readme would then have a link to where\r\n the old one could be downloaded be it the chebfun website or github.\r\n <\/p>\r\n

Backward compatibility is obviously a challenge for the File Exchange. The integration with GitHub has helped but for files\r\n not linked to GitHub it can be difficult to impossible to get older versions of code when a file is updated.\r\n <\/p>\r\n

What are your thoughts<\/a> on the idea of a readme, multiple versions of a tool on the File Exchange, and the importance of backward compatibility on\r\n the File Exchange? Is this a challenge you've struggled with?\r\n <\/p>\r\n

We also discussed content curation on the File Exchange. There currently is none outside of ensuring export control compliance.\r\n Do you think that content on the File Exchange should be curated in some way?\r\n <\/p>\r\n

Comments<\/a><\/h3>\r\n

Give the latest version of chebfun a try and let us know what you think here<\/a> or leave a comment<\/a> for the Chebfun Team.\r\n <\/p>