On Fri, Feb 18, 2022 at 03:45:18AM -0500, Mike Marchywka wrote:
> On Thu, Feb 17, 2022 at 10:00:31PM -0500, Liam Healy wrote:
> >This thread seems relevant; as of 2015 or so, the answer was "most
> > probably not":
> >
> > [https://github.com/openjournals/brief-ideas/issues/132#issuecommen
On Thu, Feb 17, 2022 at 10:00:31PM -0500, Liam Healy wrote:
>This thread seems relevant; as of 2015 or so, the answer was "most
> probably not":
>
> [https://github.com/openjournals/brief-ideas/issues/132#issuecomment-164936220]https://github.com/openjournals/brief-ideas/
>issues/132#i
I like the idea of a DOI. Also the gnu.org website is pretty stable and
for citing purposes, I think using the technical report aspect of bibtex
with a link to the gnu.org site should be fine.
On 2/17/22 11:33, Mark Galassi wrote:
I suggest archiving on Zenodo https://zenodo.org/
Zenodo works
This thread seems relevant; as of 2015 or so, the answer was "most probably
not":
https://github.com/openjournals/brief-ideas/issues/132#issuecomment-164936220
and if you scroll all the way to the bottom through many "any updates on
this?" postings,
you'll see postings from a few days ago saying ba
Patrick,
Regarding publishing ... I am not an expert in numerical analysis and
literature, so my comments may be off here. Still,
In your memory layout and access optimization section (Section 5) you do
not cite any prior literature on this technique applied to Legendre
Polynomial evaluation.
T
> I suggest archiving on Zenodo https://zenodo.org/
Zenodo works well for this and gives you a citable location and a DOI; I put
the gsl design document on there, so if you create a gsl community then we can
have 2 things :-)
On Thu, Feb 17, 2022 at 11:32:27AM -0500, Liam Healy wrote:
> I suggest archiving on Zenodo https://zenodo.org/. This will provide
> permanent storage and a DOI. Subsequent revisions will get their own DOI,
> but there is also a generic DOI. You can even make a GSL "community"
> https://zenodo.org/
I suggest archiving on Zenodo https://zenodo.org/. This will provide
permanent storage and a DOI. Subsequent revisions will get their own DOI,
but there is also a generic DOI. You can even make a GSL "community"
https://zenodo.org/communities/.
On Thu, Feb 17, 2022 at 4:21 AM Mike Marchywka
wrote
On Wed, Feb 16, 2022 at 11:24:53PM -0700, Patrick Alken wrote:
> Thanks Mark,
>
> I don't think it is suitable for publication in a journal.
> There is nothing novel here, its just technical details of how
> to calculate ALFs efficiently.
But how should other people cite your work? This is a re
Thanks Mark,
I don't think it is suitable for publication in a journal. There is
nothing novel here, its just technical details of how to calculate ALFs
efficiently.
I'll see if I can fix the formatting issue on eq. 36. Its a good idea to
cite GSL, I will add that :)
Patrick
On 2/16/22
Patrick, this is a great paper. It shows the same care you apply to
maintaining gsl. The writing is also very clear, and I love the table of
acronyms :-). Do you plan to submit for publication in a numerical analysis
journal, or submit to the arXiv?
The only previous quasi-report had been
Hello all,
I have recently re-written the array versions of the Associated
Legendre functions (gsl_sf_legendre) to be much more efficient. The
factors in the recurrence relations are now precomputed, and they are
stored in a memory layout to maximize cache efficiency. The result is a
signif
12 matches
Mail list logo