What I would do is:
- Write the code and put it on a ticket.
- Post the paper on the arXiv, citing Sage.
- Reference the arXiv version in the initial patch just saying preprint.
- Change the reference once the paper is accepted and published (which is
super easy, and it's not like we have a short
> The simplest solution is to write the code up in a my_code.sage file,
> post it somewhere, and include examples in your paper.
If you do that or if you try the '.spkg' approach, be careful that the
code you need is available in the *latest stable release* and not only
in the latest beta.
With t
On Thu, Aug 20, 2015 at 2:17 PM, Michael Orlitzky wrote:
> I'm working on a paper where we coin a new term and implement a new
> algorithm. I'd like to cite Sage as an implementation, but then I have a
> chicken and egg problem.
>
> I'd like the code to work before we submit the paper.. but to do
I'm working on a paper where we coin a new term and implement a new
algorithm. I'd like to cite Sage as an implementation, but then I have a
chicken and egg problem.
I'd like the code to work before we submit the paper.. but to do that, I
need to add a method that only appears in our paper. The on