-
-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cycle 4 funding: uncertainties, masks, quantities, other types of arrays #380
Conversation
If I can give more than 👍 , I would. Your frequent contributions are invaluable! |
finance/proposal-calls/cycle4/mhvk-uncertainty-masked-units-development.md
Show resolved
Hide resolved
So happy to see this request @mhvk ! Do you envision this funding coming to you directly as a contractor or through your university and charged overhead? In order for us to have a realistic cost estimate for this work, we need to have that detail figured out at this stage. Currently, we are funded by a NASA grant and we'll also need to doublecheck if we can subaward to Canada. |
@kelle - I think for me paying the university would be easier (no worries about pension contributions, health benefits and things like that), but indeed I do not know whether they would charge anything beyond the fraction of my salary covered. I'll talk to my chair! |
Great news! This work is fundable by the NASA grant since it is technically "software engineering" work. I will followup with you over email/Slack to discuss details. |
Updated the PR, mostly to add explicit links to @nstarman's really nice discussion of Quantity 2.0, which means that my piece can be about implementing |
Please react to this comment to vote on this proposal (👍, 👎, or no reaction for +0) |
@mhvk Do you have any update on your budget after discussing with your Chair? Is 54,000 still an accurate 1 year budget? |
I haven't gotten much further than hearing it is definitely possible, and that likely any pay would be directly to me. The latter is a bit annoying for me (pension, etc.), but it means it is all easier at least in terms of dollar figures. Anyway, bottom line: the amount is still good. |
Hi Marten, I'm writing on behalf of Astropy's Finance Committee regarding the outcome of your recent funding request PR#380. We have opened a new issue #418 to track the progress. We are pleased to be able to let you know that, following consultation with the community, we are able to approve this request. We can currently fund the Year 1 amount of $54,000.00 (US) to carry out the project. Funding beyond this amount will be contingent upon the availability of funds. (We will be using the full budgets of all of the approved requests to craft future grant and funding proposals.) Ana Gabela and I will be your contacts on the Finance Committee to facilitate this award. Please get in touch with us if you have any questions or concerns. Please do not reach out to NumFOCUS directly. In addition, new to this funding cycle, is the assignment of a COTR (Contracting Officer's Technical Representative) to each funded project. This concept is borrowed from government funding agencies, although it is to be stressed that Astropy's goal is to make the COTR role as low-overhead as possible. The COTR’s primary responsibility is to make sure the work is happening at the expected pace and, if necessary, to be a liaison between the funded project and the Finance Committee or CoCo. The COTR for your project will be assigned shortly and we’ll also be sending out more details about how we see this working. The next steps are: Please make sure that you are registered with Open Collective (https://opencollective.com/): this is the system you will use to submit your invoices for payment. Note that your invoices should be submitted through the NASA project on Open Collective. We expect the work to be carried out between 2024-05-01 and 2024-04-31 (the “period of performance”). This can be edited based on University of Toronto policies. Congratulations --- we are really looking forward to seeing you put these funds to good use! Aarya on behalf of the Astropy Finance Committee |
A perhaps wild idea to allow myself more time for moving astropy core forward. Will need checking with the University of Toronto on what's possible.