Re: First ever GSL Technical Report (ALFs)
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#issuecomment-164936220]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 basically nothing's > > changed. > >I just checked some of my papers on Zenodo, and none came up in GS. I went to google scolar and typed in "zenodo" and after the papers ABOUT Zenodo there seemed to be several that are on Zenodo. As it seems to be affiliated with CERN, it has all the right credentials. However, GS may curate them by some unknown rules. Their DOI url will redirect to their zenodo web pages but apparently can not be used to get the bibtex info without scraping the Zenodo site. Most publishers make the citation info available through crossref making it easier to cite from a DOI. However, as I search for click-through tracking, the DOI url's make a natural as they all go to the same domain and right now their server does not seem to mind a made up query string. So, if you want their server to know the work that created your curiosity, you could make your bibliography contain DOI links with your DOI in the query string - then you just need to get them to count and disseminate the results :) > > I started using researchgate and academia.edu a couple years ago and monitored > GS indexing. Most of these come up a week or so after posting but > they may curate them hard to know, > > https://www.researchgate.net/profile/Mike_Marchywka > > Again, researchgate generates a DOI but I'm not sure it is useful > for getting bibliographic information since neither it nor the one > I checked from Zenodo worked with crossref. > > Googgle Scholar does have a way to generate bibtex from an indexed result > but last time I looked it was very terse or incomplete. When I find hits > on GS I don't use their cite facilities but put the link into Toobib > ( others may use Zotero ). In any case, once a document is downloaded > you may still want to cite it but I don't see anyone other than myself > advocating a method to include machine readable citation information. > Also there is another annoyance in the lack of being able to know > when a document generates interest as with a user clicking on a > bibliographic citation. I'm working on a modifying bibliographies > in documents I gnerate to put a doc identifier ( maybe a DOI when > a useful one exists ) in the query string so a server could > attribute the click to the work. Or, maybe do as google does > and wrap the entire URL into a central passthrough server > so it can cound the clicks before redirecting to the > real location :) > > > >On Thu, Feb 17, 2022 at 12:25 PM Mike Marchywka > > <[mailto:marchy...@hotmail.com]marchy...@hotmail.com> wrote: > > > > On Thu, Feb 17, 2022 at 11:32:27AM -0500, Liam Healy wrote: > > > I suggest archiving on Zenodo > > [https://zenodo.org/]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/]https://zenodo.org/communities/. > > Do you know if google scholar indexes these? It looks like > > they index most of researchgate and [http://academia.edu/]academia.edu. > > Researhgate creates a DOI but apparently they don't tell "Crossref" > > about it so it is hard to cite ( if anyone know differently great). > > In any case, the output document ( usually pdf ) should have > > machine readable info in the extended information if you want > > people to easily cite it. This can be hard since you don't > > know where it is going and can't put in a url etc. The bibtex > > download software can put on the finishing touches however. > > I just took a random page, > > > > [https://zenodo.org/record/6126333#.Yg6CHnXMJCW]https://zenodo.org/record/6126333#.Yg6CHnXMJCW > > and TooBib tried to look up the DOI, > > > > [http://api.crossref.org/works/10.5281/zenodo.6126333]http://api.crossref.org/works/10.5281/zenodo.6126333 > > which returned a 404. This seems to be the right > > DOI as displayed on the page, > > February 17, 2022 > > DOI: > > 10.5281/zenodo.6126333 > > Keyword(s): > > However, toobib did find a citation using a standard method whereas > > with researchgate it is a struggle, > > % mjmhandler: toobib handleadhochtml<-citation > > % date 2022-02-17:12:07:12 Thu Feb 17 12:07:12 EST 2022 > > % srcurl: > >
Re: First ever GSL Technical Report (ALFs)
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#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 basically nothing's changed.
>I just checked some of my papers on Zenodo, and none came up in GS.
I started using researchgate and academia.edu a couple years ago and monitored
GS indexing. Most of these come up a week or so after posting but
they may curate them hard to know,
https://www.researchgate.net/profile/Mike_Marchywka
Again, researchgate generates a DOI but I'm not sure it is useful
for getting bibliographic information since neither it nor the one
I checked from Zenodo worked with crossref.
Googgle Scholar does have a way to generate bibtex from an indexed result
but last time I looked it was very terse or incomplete. When I find hits
on GS I don't use their cite facilities but put the link into Toobib
( others may use Zotero ). In any case, once a document is downloaded
you may still want to cite it but I don't see anyone other than myself
advocating a method to include machine readable citation information.
Also there is another annoyance in the lack of being able to know
when a document generates interest as with a user clicking on a
bibliographic citation. I'm working on a modifying bibliographies
in documents I gnerate to put a doc identifier ( maybe a DOI when
a useful one exists ) in the query string so a server could
attribute the click to the work. Or, maybe do as google does
and wrap the entire URL into a central passthrough server
so it can cound the clicks before redirecting to the
real location :)
>On Thu, Feb 17, 2022 at 12:25 PM Mike Marchywka
> <[mailto:marchy...@hotmail.com]marchy...@hotmail.com> wrote:
>
> On Thu, Feb 17, 2022 at 11:32:27AM -0500, Liam Healy wrote:
> > I suggest archiving on Zenodo
> [https://zenodo.org/]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/]https://zenodo.org/communities/.
> Do you know if google scholar indexes these? It looks like
> they index most of researchgate and [http://academia.edu/]academia.edu.
> Researhgate creates a DOI but apparently they don't tell "Crossref"
> about it so it is hard to cite ( if anyone know differently great).
> In any case, the output document ( usually pdf ) should have
> machine readable info in the extended information if you want
> people to easily cite it. This can be hard since you don't
> know where it is going and can't put in a url etc. The bibtex
> download software can put on the finishing touches however.
> I just took a random page,
>
> [https://zenodo.org/record/6126333#.Yg6CHnXMJCW]https://zenodo.org/record/6126333#.Yg6CHnXMJCW
> and TooBib tried to look up the DOI,
>
> [http://api.crossref.org/works/10.5281/zenodo.6126333]http://api.crossref.org/works/10.5281/zenodo.6126333
> which returned a 404. This seems to be the right
> DOI as displayed on the page,
> February 17, 2022
> DOI:
> 10.5281/zenodo.6126333
> Keyword(s):
> However, toobib did find a citation using a standard method whereas
> with researchgate it is a struggle,
> % mjmhandler: toobib handleadhochtml<-citation
> % date 2022-02-17:12:07:12 Thu Feb 17 12:07:12 EST 2022
> % srcurl:
> [https://zenodo.org/record/6126333#.Yg6An3XMJCU]https://zenodo.org/record/6126333#.Yg6An3XMJCU
> % citeurl:
> [https://zenodo.org/record/6126333#.Yg6An3XMJCU]https://zenodo.org/record/6126333#.Yg6An3XMJCU
> @article{processeddataYangKalverla,
> X_TooBib = {date: FixBeKvp s=2022/02/17 cmd=date -f - "+%Y-%m-%d"
> d=2022-02-17 dn=date},
> X_TooBib = {year: ReWriteKvp dn=year sn=date flags=4},
> X_TooBib = {month: ReWriteKvp dn=month sn=date flags=7},
> X_TooBib = {day: ReWriteKvp dn=day sn=date flags=7},
> X_TooBib = {publisher: ReWriteParse be.get(s)= be.get(dest)=},
> X_TooBib = {journal: ReWriteParse be.get(s)= be.get(dest)=},
> X_TooBib = {urldate: FixBeKvp s= cmd=date "+%Y-%m-%d" d=2022-02-17
> dn=urldate},
> X_TooBib = {author: Liu , Yang and Kalverla , Peter and Alidoost ,
> Fakhereh and Verhoeven , Stefan and Vreede ,
> Barbara and Booth , Ben and Coppola , Erika and Nogherotto , Rita and
> Brunner , Lukas and Harris , Glen and Qasmi
> , Said and Ballinger , Andrew and Hegerl , Gabriele and McSweeney ,
> Carol and O ' Reilly , Christopher and Palmer ,
> Tamzin
Re: First ever GSL Technical Report (ALFs)
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 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 :-)
Re: First ever GSL Technical Report (ALFs)
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 basically nothing's changed.
I just checked some of my papers on Zenodo, and none came up in GS.
On Thu, Feb 17, 2022 at 12:25 PM Mike Marchywka
wrote:
> 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/communities/.
>
> Do you know if google scholar indexes these? It looks like
> they index most of researchgate and academia.edu.
>
> Researhgate creates a DOI but apparently they don't tell "Crossref"
> about it so it is hard to cite ( if anyone know differently great).
> In any case, the output document ( usually pdf ) should have
> machine readable info in the extended information if you want
> people to easily cite it. This can be hard since you don't
> know where it is going and can't put in a url etc. The bibtex
> download software can put on the finishing touches however.
>
> I just took a random page,
>
> https://zenodo.org/record/6126333#.Yg6CHnXMJCW
>
> and TooBib tried to look up the DOI,
>
> http://api.crossref.org/works/10.5281/zenodo.6126333
>
> which returned a 404. This seems to be the right
> DOI as displayed on the page,
>
> February 17, 2022
> DOI:
> 10.5281/zenodo.6126333
> Keyword(s):
>
> However, toobib did find a citation using a standard method whereas
> with researchgate it is a struggle,
>
> % mjmhandler: toobib handleadhochtml<-citation
> % date 2022-02-17:12:07:12 Thu Feb 17 12:07:12 EST 2022
> % srcurl: https://zenodo.org/record/6126333#.Yg6An3XMJCU
> % citeurl: https://zenodo.org/record/6126333#.Yg6An3XMJCU
> @article{processeddataYangKalverla,
> X_TooBib = {date: FixBeKvp s=2022/02/17 cmd=date -f - "+%Y-%m-%d"
> d=2022-02-17 dn=date},
> X_TooBib = {year: ReWriteKvp dn=year sn=date flags=4},
> X_TooBib = {month: ReWriteKvp dn=month sn=date flags=7},
> X_TooBib = {day: ReWriteKvp dn=day sn=date flags=7},
> X_TooBib = {publisher: ReWriteParse be.get(s)= be.get(dest)=},
> X_TooBib = {journal: ReWriteParse be.get(s)= be.get(dest)=},
> X_TooBib = {urldate: FixBeKvp s= cmd=date "+%Y-%m-%d" d=2022-02-17
> dn=urldate},
> X_TooBib = {author: Liu , Yang and Kalverla , Peter and Alidoost ,
> Fakhereh and Verhoeven , Stefan and Vreede , Barbara and Booth , Ben
> and Coppola , Erika and Nogherotto , Rita and Brunner , Lukas and
> Harris , Glen and Qasmi , Said and Ballinger , Andrew and Hegerl ,
> Gabriele and McSweeney , Carol and O ' Reilly , Christopher and Palmer ,
> Tamzin and Ribes , Aurélien and de Vries , Hylke},
> abstract_html_url = {https://zenodo.org/record/6126333},
> author = { Liu , Yang and Kalverla , Peter and Alidoost , Fakhereh and
> Verhoeven , Stefan and Vreede , Barbara and Booth , Ben and Coppola ,
> Erika and Nogherotto , Rita and Brunner , Lukas and Harris , Glen and
> Qasmi , Said and Ballinger , Andrew and Hegerl , Gabriele and McSweeney
> , Carol and O ' Reilly , Christopher and Palmer , Tamzin and Ribes ,
> Aurélien and de Vries , Hylke},
> author_orig = {Liu, Yang and Kalverla, Peter and Alidoost, Fakhereh and
> Verhoeven, Stefan and Vreede, Barbara and Booth, Ben and Coppola, Erika and
> Nogherotto, Rita and Brunner, Lukas and Harris, Glen and Qasmi, Said and
> Ballinger, Andrew and Hegerl, Gabriele and McSweeney, Carol and O'Reilly,
> Christopher and Palmer, Tamzin and Ribes, Aurélien and de Vries, Hylke},
> date = {2022-02-17},
> day = {17},
> doi = {10.5281/zenodo.6126333},
> keywords = {climate and EUCP},
> month = {02},
> pagetitle = {Pre-processed data of atlas in EUCP-WP2 | Zenodo},
> publication_date = {2022/02/17},
> title = {Pre-processed data of atlas in EUCP-WP2},
> urldate = {2022-02-17},
> year = {2022},
> url={https://zenodo.org/record/6126333#.Yg6An3XMJCU},
> srcurl={https://zenodo.org/record/6126333#.Yg6An3XMJCU},
> xsrcurl={https://zenodo.org/record/6126333#.Yg6An3XMJCU},
> citeurl={https://zenodo.org/record/6126333#.Yg6An3XMJCU}
>
> }
>
>
>
>
> >
> > 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 recurring problem
> > > for me and I have created a developmental tool maybe similar to
> > > Zotero for obtaining bibtex from many random links. When I post
> > > pdf "tech reports", for example,
> > >
> > >
Re: First ever GSL Technical Report (ALFs)
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.
This suggests that your approach is novel and therefore merits publication.
Thanks (for reading this, and for writing the very nice report)
Mirko
On Thu, Feb 17, 2022 at 1:25 AM 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.
>
> 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 22:51, Mark Galassi wrote:
> > 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 the ongoing design document that
> I kept going with James and Brian in the early years, but it is a working
> design doc, not anything of the scope you have shown here.
> >
> > Tiny suggestions: alignment of equation 36 on page 5: "l >= 1" could be
> moved quite a bit to the left. Maybe an extra & to make it match the start
> of the l >= 1, m > 0.
> >
> > You might also want to also cite the reference manual (as we ask people
> to do when they use gsl :-) ). A recent bibtex skeleton on that is the
> 2019 Network Theory edition.
> >
> > @book{gslteam2019gnuscientificlibrary,
> >title={GNU Scientific Library Reference Manual},
> >author={Galassi, Mark and Davies, Jim and Theiler, James and Gough,
> Brian and Jungman, Gerard and Alken, Patrick and Booth, Michael and Rossi,
> Fabrice and Ulerich, Rhys},
> >year={2019},
> >isbn={9780954612078},
> >publisher={Network Theory Limited}
> > }
>
>
Re: First ever GSL Technical Report (ALFs)
> 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 :-)
Re: First ever GSL Technical Report (ALFs)
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/communities/.
Do you know if google scholar indexes these? It looks like
they index most of researchgate and academia.edu.
Researhgate creates a DOI but apparently they don't tell "Crossref"
about it so it is hard to cite ( if anyone know differently great).
In any case, the output document ( usually pdf ) should have
machine readable info in the extended information if you want
people to easily cite it. This can be hard since you don't
know where it is going and can't put in a url etc. The bibtex
download software can put on the finishing touches however.
I just took a random page,
https://zenodo.org/record/6126333#.Yg6CHnXMJCW
and TooBib tried to look up the DOI,
http://api.crossref.org/works/10.5281/zenodo.6126333
which returned a 404. This seems to be the right
DOI as displayed on the page,
February 17, 2022
DOI:
10.5281/zenodo.6126333
Keyword(s):
However, toobib did find a citation using a standard method whereas
with researchgate it is a struggle,
% mjmhandler: toobib handleadhochtml<-citation
% date 2022-02-17:12:07:12 Thu Feb 17 12:07:12 EST 2022
% srcurl: https://zenodo.org/record/6126333#.Yg6An3XMJCU
% citeurl: https://zenodo.org/record/6126333#.Yg6An3XMJCU
@article{processeddataYangKalverla,
X_TooBib = {date: FixBeKvp s=2022/02/17 cmd=date -f - "+%Y-%m-%d" d=2022-02-17
dn=date},
X_TooBib = {year: ReWriteKvp dn=year sn=date flags=4},
X_TooBib = {month: ReWriteKvp dn=month sn=date flags=7},
X_TooBib = {day: ReWriteKvp dn=day sn=date flags=7},
X_TooBib = {publisher: ReWriteParse be.get(s)= be.get(dest)=},
X_TooBib = {journal: ReWriteParse be.get(s)= be.get(dest)=},
X_TooBib = {urldate: FixBeKvp s= cmd=date "+%Y-%m-%d" d=2022-02-17 dn=urldate},
X_TooBib = {author: Liu , Yang and Kalverla , Peter and Alidoost , Fakhereh
and Verhoeven , Stefan and Vreede , Barbara and Booth , Ben and Coppola ,
Erika and Nogherotto , Rita and Brunner , Lukas and Harris , Glen and Qasmi
, Said and Ballinger , Andrew and Hegerl , Gabriele and McSweeney , Carol
and O ' Reilly , Christopher and Palmer , Tamzin and Ribes , Aurélien and
de Vries , Hylke},
abstract_html_url = {https://zenodo.org/record/6126333},
author = { Liu , Yang and Kalverla , Peter and Alidoost , Fakhereh and
Verhoeven , Stefan and Vreede , Barbara and Booth , Ben and Coppola , Erika
and Nogherotto , Rita and Brunner , Lukas and Harris , Glen and Qasmi ,
Said and Ballinger , Andrew and Hegerl , Gabriele and McSweeney , Carol and
O ' Reilly , Christopher and Palmer , Tamzin and Ribes , Aurélien and de
Vries , Hylke},
author_orig = {Liu, Yang and Kalverla, Peter and Alidoost, Fakhereh and
Verhoeven, Stefan and Vreede, Barbara and Booth, Ben and Coppola, Erika and
Nogherotto, Rita and Brunner, Lukas and Harris, Glen and Qasmi, Said and
Ballinger, Andrew and Hegerl, Gabriele and McSweeney, Carol and O'Reilly,
Christopher and Palmer, Tamzin and Ribes, Aurélien and de Vries, Hylke},
date = {2022-02-17},
day = {17},
doi = {10.5281/zenodo.6126333},
keywords = {climate and EUCP},
month = {02},
pagetitle = {Pre-processed data of atlas in EUCP-WP2 | Zenodo},
publication_date = {2022/02/17},
title = {Pre-processed data of atlas in EUCP-WP2},
urldate = {2022-02-17},
year = {2022},
url={https://zenodo.org/record/6126333#.Yg6An3XMJCU},
srcurl={https://zenodo.org/record/6126333#.Yg6An3XMJCU},
xsrcurl={https://zenodo.org/record/6126333#.Yg6An3XMJCU},
citeurl={https://zenodo.org/record/6126333#.Yg6An3XMJCU}
}
>
> 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 recurring problem
> > for me and I have created a developmental tool maybe similar to
> > Zotero for obtaining bibtex from many random links. When I post
> > pdf "tech reports", for example,
> >
> > https://www.researchgate.net/profile/Mike_Marchywka
> >
> > I try to include human AND machine readable bibtex.
> > If you look at any of my recent pdf files there is always a suggsted
> > version at the end although I'm not sure if Zotero or Toobib
> > can find that. In the extended information I include
> > bibtex info but have not found a well accepted or commonly
> > used way to do this ( tug.org website in particular does not
> > seem to have an easy way to cite their works unless you know
> > about their lookup -table page )
> > Its not hard to do this with latex and I can contribute
> > the few lines I use to do it
Re: First ever GSL Technical Report (ALFs)
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 recurring problem
> for me and I have created a developmental tool maybe similar to
> Zotero for obtaining bibtex from many random links. When I post
> pdf "tech reports", for example,
>
> https://www.researchgate.net/profile/Mike_Marchywka
>
> I try to include human AND machine readable bibtex.
> If you look at any of my recent pdf files there is always a suggsted
> version at the end although I'm not sure if Zotero or Toobib
> can find that. In the extended information I include
> bibtex info but have not found a well accepted or commonly
> used way to do this ( tug.org website in particular does not
> seem to have an easy way to cite their works unless you know
> about their lookup -table page )
> Its not hard to do this with latex and I can contribute
> the few lines I use to do it if anyone wants it.
>
> For example,
> exifutil -list covidup.pdf
> ExifTool Version Number : 11.75
> File Name : covidup.pdf
> Directory : .
> File Size : 417 kB
> File Modification Date/Time : 2022:02:16 18:11:39-05:00
> File Access Date/Time : 2022:02:16 19:50:21-05:00
> File Inode Change Date/Time : 2022:02:16 18:11:39-05:00
> File Permissions: rw-rw-r--
> File Type : PDF
> File Type Extension : pdf
> MIME Type : application/pdf
> PDF Version : 1.5
> Linearized : No
> Page Count : 31
> Page Mode : UseOutlines
> Author :
> Title :
> Subject :
> Creator : LaTeX with hyperref package
> Producer: LuaTeX-0.80.0
> X-bib-filename : covidup
> X-bib-run-date : February 16, 2022
> X-bib-title : An Update: On the age distribution of
> SARS-Cov-2 Patients
> X-bib-author: Mike J Marchywka
> X-bib-type : techreport
> X-bib-name : marchywka-MJM-2021-007
> X-bib-number: MJM-2021-007
> X-bib-version : 0.00
> X-bib-institution : not institutionalized, independent
> X-bib-address : 306 Charles Cox , Canton GA 30115
> X-bib-date : February 16, 2022
> X-bib-startdate : 2021-07-21
> X-bib-day : 16
> X-bib-month : 2
> X-bib-year : 2022
> X-bib-author 1email : marchy...@hotmail.com
> X-bib-contact : marchy...@hotmail.com
> X-bib-author 1id: orcid.org/-0001-9237-455X
> X-bib-pages : 31
> X-bib-bibtex: @techreport{marchywka-MJM-2021-007,
> filename ="covidup" , run-date ="February 16, 2022" , title ="An Update: On
> the age distribution of SARS-Cov-2 Patients " , author ="Mike J Marchywka "
> , type ="techreport" , name ="marchywka-MJM-2021-007" , number
> ="MJM-2021-007" , version ="0.00" , institution ="not institutionalized,
> independent " , address =" 306 Charles Cox , Canton GA 30115" , date
> ="February 16, 2022" , startdate ="2021-07-21" , day ="16" , month ="2" ,
> year ="2022" , author1email ="marchy...@hotmail.com" , contact ="
> marchy...@hotmail.com" , author1id ="orcid.org/-0001-9237-455X" ,
> pages =" 31" }
> Create Date : 2022:02:16 18:11:38-05:00
> Modify Date : 2022:02:16 18:11:38-05:00
> Trapped : False
> PTEX Fullbanner : This is LuaTeX, Version beta-0.80.0 (TeX
> Live 2015/Debian) (rev 5238)
>
>
>
> >
> > 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 22:51, Mark Galassi wrote:
> > > 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 the ongoing design document
> that I kept going with James and Brian in the early years, but it is a
> working design doc, not
Re: First ever GSL Technical Report (ALFs)
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 recurring problem
for me and I have created a developmental tool maybe similar to
Zotero for obtaining bibtex from many random links. When I post
pdf "tech reports", for example,
https://www.researchgate.net/profile/Mike_Marchywka
I try to include human AND machine readable bibtex.
If you look at any of my recent pdf files there is always a suggsted
version at the end although I'm not sure if Zotero or Toobib
can find that. In the extended information I include
bibtex info but have not found a well accepted or commonly
used way to do this ( tug.org website in particular does not
seem to have an easy way to cite their works unless you know
about their lookup -table page )
Its not hard to do this with latex and I can contribute
the few lines I use to do it if anyone wants it.
For example,
exifutil -list covidup.pdf
ExifTool Version Number : 11.75
File Name : covidup.pdf
Directory : .
File Size : 417 kB
File Modification Date/Time : 2022:02:16 18:11:39-05:00
File Access Date/Time : 2022:02:16 19:50:21-05:00
File Inode Change Date/Time : 2022:02:16 18:11:39-05:00
File Permissions: rw-rw-r--
File Type : PDF
File Type Extension : pdf
MIME Type : application/pdf
PDF Version : 1.5
Linearized : No
Page Count : 31
Page Mode : UseOutlines
Author :
Title :
Subject :
Creator : LaTeX with hyperref package
Producer: LuaTeX-0.80.0
X-bib-filename : covidup
X-bib-run-date : February 16, 2022
X-bib-title : An Update: On the age distribution of
SARS-Cov-2 Patients
X-bib-author: Mike J Marchywka
X-bib-type : techreport
X-bib-name : marchywka-MJM-2021-007
X-bib-number: MJM-2021-007
X-bib-version : 0.00
X-bib-institution : not institutionalized, independent
X-bib-address : 306 Charles Cox , Canton GA 30115
X-bib-date : February 16, 2022
X-bib-startdate : 2021-07-21
X-bib-day : 16
X-bib-month : 2
X-bib-year : 2022
X-bib-author 1email : marchy...@hotmail.com
X-bib-contact : marchy...@hotmail.com
X-bib-author 1id: orcid.org/-0001-9237-455X
X-bib-pages : 31
X-bib-bibtex: @techreport{marchywka-MJM-2021-007, filename
="covidup" , run-date ="February 16, 2022" , title ="An Update: On the age
distribution of SARS-Cov-2 Patients " , author ="Mike J Marchywka " , type
="techreport" , name ="marchywka-MJM-2021-007" , number ="MJM-2021-007" ,
version ="0.00" , institution ="not institutionalized, independent " , address
=" 306 Charles Cox , Canton GA 30115" , date ="February 16, 2022" , startdate
="2021-07-21" , day ="16" , month ="2" , year ="2022" , author1email
="marchy...@hotmail.com" , contact ="marchy...@hotmail.com" , author1id
="orcid.org/-0001-9237-455X" , pages =" 31" }
Create Date : 2022:02:16 18:11:38-05:00
Modify Date : 2022:02:16 18:11:38-05:00
Trapped : False
PTEX Fullbanner : This is LuaTeX, Version beta-0.80.0 (TeX Live
2015/Debian) (rev 5238)
>
> 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 22:51, Mark Galassi wrote:
> > 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 the ongoing design document that I
> > kept going with James and Brian in the early years, but it is a working
> > design doc, not anything of the scope you have shown here.
> >
> > Tiny suggestions: alignment of equation 36 on page 5: "l >= 1" could be
> > moved quite a bit to the left. Maybe an extra & to make it match the start
> > of the l >= 1, m > 0.
> >
> > You might also want to also cite the reference manual (as we ask people to
> > do when they use gsl :-) ). A recent bibtex skeleton on that is the 2019
> > Network Theory edition.
> >
> >
Re: First ever GSL Technical Report (ALFs)
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 22:51, Mark Galassi wrote:
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 the ongoing design document that I kept
going with James and Brian in the early years, but it is a working design doc,
not anything of the scope you have shown here.
Tiny suggestions: alignment of equation 36 on page 5: "l >= 1" could be moved quite a bit
to the left. Maybe an extra & to make it match the start of the l >= 1, m > 0.
You might also want to also cite the reference manual (as we ask people to do
when they use gsl :-) ). A recent bibtex skeleton on that is the 2019 Network
Theory edition.
@book{gslteam2019gnuscientificlibrary,
title={GNU Scientific Library Reference Manual},
author={Galassi, Mark and Davies, Jim and Theiler, James and Gough, Brian
and Jungman, Gerard and Alken, Patrick and Booth, Michael and Rossi, Fabrice
and Ulerich, Rhys},
year={2019},
isbn={9780954612078},
publisher={Network Theory Limited}
}
Re: First ever GSL Technical Report (ALFs)
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 the ongoing design document that I kept
going with James and Brian in the early years, but it is a working design doc,
not anything of the scope you have shown here.
Tiny suggestions: alignment of equation 36 on page 5: "l >= 1" could be moved
quite a bit to the left. Maybe an extra & to make it match the start of the l
>= 1, m > 0.
You might also want to also cite the reference manual (as we ask people to do
when they use gsl :-) ). A recent bibtex skeleton on that is the 2019 Network
Theory edition.
@book{gslteam2019gnuscientificlibrary,
title={GNU Scientific Library Reference Manual},
author={Galassi, Mark and Davies, Jim and Theiler, James and Gough, Brian and
Jungman, Gerard and Alken, Patrick and Booth, Michael and Rossi, Fabrice and
Ulerich, Rhys},
year={2019},
isbn={9780954612078},
publisher={Network Theory Limited}
}
