[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: First ever GSL Technical Report (ALFs)
From: |
Mike Marchywka |
Subject: |
Re: First ever GSL Technical Report (ALFs) |
Date: |
Thu, 17 Feb 2022 03:39:05 -0500 |
User-agent: |
NeoMutt/20171215 |
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 : marchywka@hotmail.com
X-bib-contact : marchywka@hotmail.com
X-bib-author 1id : orcid.org/0000-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
="marchywka@hotmail.com" , contact ="marchywka@hotmail.com" , author1id
="orcid.org/0000-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.
> >
> > @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}
> > }
>
--
mike marchywka
306 charles cox
canton GA 30115
USA, Earth
marchywka@hotmail.com
404-788-1216
ORCID: 0000-0001-9237-455X
- First ever GSL Technical Report (ALFs), Patrick Alken, 2022/02/16
- Re: First ever GSL Technical Report (ALFs), Mark Galassi, 2022/02/17
- Re: First ever GSL Technical Report (ALFs), Patrick Alken, 2022/02/17
- Re: First ever GSL Technical Report (ALFs),
Mike Marchywka <=
- Re: First ever GSL Technical Report (ALFs), Liam Healy, 2022/02/17
- Re: First ever GSL Technical Report (ALFs), Mike Marchywka, 2022/02/17
- Re: First ever GSL Technical Report (ALFs), Liam Healy, 2022/02/17
- Re: First ever GSL Technical Report (ALFs), Mike Marchywka, 2022/02/18
- Re: First ever GSL Technical Report (ALFs), Mike Marchywka, 2022/02/18
- Re: First ever GSL Technical Report (ALFs), Mark Galassi, 2022/02/17
- Re: First ever GSL Technical Report (ALFs), Patrick Alken, 2022/02/17
- Re: First ever GSL Technical Report (ALFs), Mirko Vukovic, 2022/02/17