---
# System prepended metadata

title: 'AAS 243: Software Funding Community Feedback'

---

# AAS 243 Software Funding Community Feedback Splinter Session
8 January 2024

[AAS Schedule Link](https://submissions.mirasmart.com/AAS243/Itinerary/EventDetail.aspx?evt=236)

Desires:
- scientists and software developers (or scientists who understand software) in review panels
- more clear guidelines on releasing open-source software when NASA civil servants are part of the project
    - *Need to direct that sort of feedback to Demitri

What funding pieces are missing?
- A lot of applications are designed to be deployed and operate in the cloud, but many places lack expertise to work on these. There is a gap in funding support for these projects.
    - AWS is a good example, people need to know how to build pipelines in interface with AWS
    - But wait! Can simply download to your own machine and process as usual....but there are egress costs and not everyone has the ability to reasonably download large amounts of data...so back to using the "in cloud" pipelines
- Could there be a bridge to simplfy how data flows to/from national HPCs. Similar to NSF ACCESS
- Same support for high energy as for optical in software libraries
    - But those efforts are usually bottom-up. OSTFL (F.7) or HPOSS (F.15) might be appropriate? It sounds like existing software with need to add new elements

Security:
- DDPR: People working internationally need to login to retrieve archives, which is problematic because of complications if multiple locations (to login) are necessary
    - Core services handle common services between discilines and data centers. Could be a solution to simplify the process while maintaining security
    - NASA could be a part of *InCommon*, which is used by other agencies such as NSF and used by international partners. Helps to simplfy data access. *InCommon* is funded by NSF and DOE


Gaps:
- Significant upstream package contributions do not have a clear funding mechanism. Many of the upstream contributions are done on *volunteer* time or funded through other means such as NSF
    - Does not always fit nicely into HPOSS, but is a possible mechanism for some development
    - HPOSS does not specify the need for using NASA data - it is for tools to be built that will be useful for people
- Training? Such as training others to useful this super cool software that's available
    - F.2 might be appropriate, but need to look closer at the language. HPOSS, in some limited instances, could also be a fit

