[Usecase] DesignSafe Use Cases Review

[Rathje, Ellen M]

Thanks, Silvia, for the reminder.  We should each correspond directly with Silvia to discuss how to update our use case.  I have!!

Thanks,
Ellen
________________________________
From: Silvia Mazzoni <silviamazzoni at yahoo.com>
Sent: Tuesday, December 3, 2024 5:47 PM
To: usecase at designsafe-ci.org <usecase at designsafe-ci.org>
Cc: Tim Cockerill <cockerill at tacc.utexas.edu>; Rathje, Ellen M <e.rathje at mail.utexas.edu>; Silvia Mazzoni <silviamazzoni at yahoo.com>
Subject: Re: DesignSafe Use Cases Review

Here I am following up on the status of Design-Safe Use Cases!!
Please, reply to this email with an update of the current status and your plans for it.
Please do not reply-all, you can just reply to me and I will provide updates to all.

To help you, use the link below for my review of each use-case.
Silvia




On Monday, November 18, 2024 at 04:59:05 PM PST, Silvia Mazzoni <silviamazzoni at yahoo.com> wrote:


All,
here is the easy-to-click link:

https://docs.google.com/spreadsheets/d/1mZB91I7j4UW1rkbQTEOo6QkMA7jGMYKdkDqIlcUrfho/edit?usp=sharing


Silvia



On Monday, November 18, 2024 at 04:28:02 PM PST, Silvia Mazzoni <silviamazzoni at yahoo.com> wrote:



NHERI-DesignSafe Use-Case Developers,

I have reviewed each Use-Case. I reviewed the documentation in terms of format and links (I have updated some links to the Jupyter notebooks). I also copied the Jupyter notebook(s) and the associated files into my local path and ran each notebook(s).

I have provided use-case-specific review notes in a google sheet as well as some general notes below that apply to all. Keep in mind that fixing the issues I found will likely reveal others, so please make sure you address them as well.

I would like to have a follow-up meeting with each use case during the first or second week of December.

USE-CASE-SPECIFIC NOTES: https://docs.google.com/spreadsheets/d/1mZB91I7j4UW1rkbQTEOo6QkMA7jGMYKdkDqIlcUrfho/edit?usp=sharing

GENERAL NOTES:

•       Headers: Each notebook should have a title, author names, affiliation and contact.

•       Publication Date: It is very important that you include publication date. This way new versions can be easily identified and compared to existing ones.

•       Notebook Documentation: Please make sure each notebook is as self-contained as possible – Very few people read documentation.

•       Missing or External Files: Some notebooks are missing files or are connecting to archive data that is not available to the public.

•       Python Libraries: Please make sure you include the required pip-installation commands in the first cells of your notebook. Here is a simple example: !pip install folium

•       Tapis V3: If your notebook submits a job to the HPC system, the code needs to be updated for Tapis V3. Profs Kumar & Arduino have developed template Notebooks in CommunityData/Jupyter-templates

•       Use-Case documentation: Wesley has created a step-by-step instructions on how to contribute/modify the documentation. I'm happy to walk through this process with you:

https://github.com/DesignSafe-CI/DS-User-Guide/tree/main/user-guide/docs/usecases#readme



Thank you,

Silvia Mazzoni

DesignSafe Applications Specialist

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.designsafe-ci.org/pipermail/usecase/attachments/20241205/705d8d0d/attachment-0001.html>