Making Igor code available on publication - best practice
Thu, 01/15/2015 - 11:53 pm
As I see it there are several options with downsides:
1. Code available on request/personal webpage - not really freely available and addresses may change etc.
2. Put code on IgorExchange - will it be here forever? Also, very bespoke code may clutter up code snippets.
3. Upload the code as a supplementary file with the paper - probably best solution but only some journals allow this, many don't.
4. Code on GitHub or some other repository - version control etc.
5. Something else?
I'd be curious as to what other people are doing, or think is best. So far we have done 1 + 2, and I'm wondering about other possibilities.