We need to backfill some events our members were involved in. Some examples would be attending conferences, earning awards, participating in outreach, etc.
Files will follow a similar template as in #2 Note that any bracketed (<>) item should be filled with item-specific information (e.g. "\" replaced with "Mapping oxygen vacancy profiles with frequency-resolved X-ray absorption spectroscopy")
@giangtle put in good effort getting this one going.
To call this one done I would like to:
[ ] Set up a repo for hosting NLEIS LabView code. Ages ago I reached out to the UW Licensing office to ask about permissions from this. We need to review UW Open Source licensing policies, and double check that hosting the files on GitHub doesn't violate any LabView licensing agreements.
[ ] Transfer frxas.py ownership to this organization. There's still a lot of documentation work before that package will be usable by the public. I don't have firm plans for completing this, but I'll start chipping away at it in the coming months.
[ ] Set up a repo for writing NLEIS analysis in Python. I'm sure we can write a module for the data collection, too, but I think that's somewhat lower priority.
[ ] Discuss if we want make the shared code repo public. Maybe nobody else cares about that one 🤣, but I appreciate the version control over digging through AdlerNAS.
For each step above we should add a link to the Software section
We need to backfill some events our members were involved in. Some examples would be attending conferences, earning awards, participating in outreach, etc.
Files will follow a similar template as in #2 Note that any bracketed (<>) item should be filled with item-specific information (e.g. "\" replaced with "Mapping oxygen vacancy profiles with frequency-resolved X-ray absorption spectroscopy")
Naming convention: yyyy-mm-dd-project.md
Contents in each file should follow
--- layout: project title: "\"
handle: \
image: /assets/images/projects/\.svg
category: project
published: true
tags: [\, \]
---
{% include JB/setup %}
\