rocco8773 Could you automate a pdf copy of the hackmd file to google docs?
Dominik Stańczak To the google drive folder with minutes? Sure, with pandoc
Dominik Stańczak Good point. I can set up a cron job for that for now, and then do some CI magic with the gdrive api later.
Dominik Stańczak And the CI stuff is easy since hackmd has auto github sync: https://github.com/PlasmaPy/plasmapy-meeting-notes/blob/master/2020-09-15.md
Dominik Stańczak No worries, take your time
jacob_schwartz Thanks to Eric for your suggestion to find existing databases. So, there's this one: https://www.nndc.bnl.gov/sigma/ which I think will have every cross section we'd need. The only part that's slightly annoying is that it's in a tabular format, since it's a Serious Business neutronics database, and that there's not rate coefficient data.
rocco8773 If NIST has a database, then that would be nice. Then you'd have a trusted source.
rocco8773 That will be a big one, we'll have to grab data from a trusted source.
jacob_schwartz From a quick search I don't think NIST has one. While it has many SRDs for atomic data, I don't see any for nuclear data other than masses and half-lives. https://www.nist.gov/srd/physicsI'm afraid the databases on the IAEA page are atomic and molecular data. Confusingly, here 'atomic' means processes dealing with electrons etc, not transformations of the nuclei.
I'll keep looking around.
rocco8773 I polled the crew on the BaPSF slack channel about this.
For atomic/molecular cross sections I got these two links:
https://www.nist.gov/pml/atomic-spectra-database
https://us.lxcat.net/data/set_type.php
For nuclear cross-sections, Troy Carter recommended:
https://www-nds.iaea.org/exfor/endf.htm
Nick Murphy ...which is a big limit to scientific reproducibility.
Nick Murphy ...but NIST data should be public domain since it's US federal government.
rocco8773 Well, if you continue reading LXCat's redistribution policy it's doesn't sound as dire as their heading. If we get contact the LXCat team (info@@lxcat.net) we might be able to work something out. Of course, that is if we decide one or more of their databases are necessary for our functionality.
rocco8773 In any event, we should probably list this sources as places to get cross-section data.
I do think our functionality should allow for the input of custom (user) databases.
Nick Murphy Also: it feels strange to not have a seven hour long Zoom meeting today.
Nick Murphy I finally got around to uploading PlasmaPy 0.4.0 to Zenodo. Still need to update the Star Fleet android personnel file.
Nick Murphy ...I mean the metaData.
Github PlasmaPy/PlasmaPy#191 : Transport eqs
Nick Murphy Yeah...I'm starting to think that using feature branches for projects that are too large for a single PR would probably be a worthwhile idea. I probably should have done that for the test helpers PR.
Nick Murphy In any case, good luck!
rocco8773 I feel your pain! It's hard to get the motivation to review large PRs.
jacob_schwartz For nuclear reaction data (Brookhaven's ENDF-6) I sent an email to the project's Dan Brown dbrown@bnl.gov to ask what license or copyrights the data might be under. I wasn't able to find anything directly from the site. I wouldn't be surprised if it were the same as NIST, since, for example, the manual describing the data format carries a paragraph: "The publisher by accepting the manuscript for publication acknowledges that the United States Government retains a non-exclusive, paid-up, irrevocable, world-wide license to publish or reproduce the published form of this manuscript, or allow others to do so, for United States Government purposes."
Nick Murphy I'll be curious what you hear back.
Dominik Stańczak > <@StanczakDominik:matrix.org> Hey, friendly reminder that the same thing is happening in an hour from now! 😆
Hey, a friendly reminder that - same as above! I wonder how deep we can go here. While we find out, here's today's agenda & minutes!
Dominik Stańczak Darn, I played myself
Dominik Stańczak > A friendly reminder that we'll be having our weekly community meeting in about 30 minutes at 18 UTC using PlasmaPy's Jitsi channel.
That's the part I wanted!
Nick Murphy Thus far, docs.plasmapy.org has been pointing to the latest version of the docs. However, that's generally most useful for developers and not as useful for people who are using the most recent release. Would it be okay if we changed docs.plasmapy.org to point to the stable version of the docs?
Nick Murphy Hm...looks like there's relevant documentation from Read the Docs here. Seems that stable gets updated automagically without us having to do anything.
Nick Murphy (Correction: winning Nintendo games...)
jacob_schwartz News back from Dave Brown at BNL (not Dan Brown ... the name of the Da Vinci Code author conspired to overwrite my reading ability).
"Jacob,
The ENDF library is public domain data as I understand it. In any event, the DOE gives it away. All we ask is that you cite the library (specifically the journal article describing the library).
The data available on the Sigma webapp hasn't been updated in a while, so you probably want to download the latest release directly. It is ENDF/B-VIII.0 at https://www.nndc.bnl.gov/endf/b8.0/download.html. The reference for the open access paper describing the release is
D.A. Brown, M.B. Chadwick, R. Capote, et al., "ENDF/B-VIII.0: The 8th Major Release of the Nuclear Reaction Data Library with CIELO-project Cross Sections, New Standards and Thermal Scattering Data", Nuclear Data Sheets, 148: pp. 1-142 (2018).I am curious what kind of data you need -- charged particle reaction data, neutron incident data or perhaps atomic data for electron and photon transport or something else entirely?
Also, would you be interested to be added the ENDF mailing list and maybe participating (virtually) in our annual Nuclear Data Week from Dec 1-4? This is the meeting where we discuss developments in the ENDF library, problems, testing, etc. Generally the folks from U. Wisconsin are our only fusion community participants, so we very much would be interested in having PPL present too.
Thanks and stay safe,
Dave "
Dominik Stańczak (learning not to overcommit, one but at a time!)