Replies: 8 comments 5 replies
|
Welcome @edison16a ! My recommendation is that you check this page and the open issues. |
|
Hi, I wanted to share a quick progress update on my GSoC 2026 application for the “Saving timestamp for each created marker” project. So far, I have:
While working on the proposal, I had one design question I wanted to confirm. Right now, my current assumption is that if a marker is duplicated, the duplicated marker should receive a new creation timestamp, since it is a newly created marker event rather than the original one. However, I wanted to check whether that is the intended behavior for InVesalius before I finalize that part in the proposal. Would the preferred behavior be:
Thanks! |
|
Hi @rmatsuda I am planning to submit the draft proposal I sent above this week through GSoC. I appreciate your guidance! Best, |
|
Hi @rmatsuda @thaismarchetti @LucasBetioli123 @vhemalheiro, I have submitted my draft proposal through the GSoC portal. I also made some updates to the proposal today, mainly regarding project saving and loading. Thank you again for the guidance, and I look forward to receiving feedback! Google Drive Link (Steps 1-3 Complete): https://drive.google.com/drive/folders/1T0vC1i4dawBHyEU2r5icUN0wGLYZ0Hsg?usp=sharing Best, |
|
Hi @rmatsuda @thaismarchetti @LucasBetioli123 @vhemalheiro, I would like to follow up and appreciate if there is any feedback on the proposal I submitted on GSoC. Thanks, |
|
Hi @rmatsuda @thaismarchetti @LucasBetioli123 @vhemalheiro, I wanted to share that I have made some updates to my proposal and uploaded the new version to the GSoC portal. I updated my college information based on my college acceptance decision to UC Berkeley, and updated the plan for weeks 7 to 8. I have also uploaded my updated resume and proposal to my Google Drive folder: Thank you so much for your guidance and support. Best, |
|
Hi @rmatsuda @thaismarchetti @LucasBetioli123 @vhemalheiro, I hope you are having a great day! I have been looking through the codebase more deeply to plan out the local testing environment, and I would like to clarify regarding the marker timestamp feature. When we use new timestamp data for the .inv3 project save pathways, is there any preference on using standard ISO 8601 strings versus a Unix epoch integer? I want to make sure the format doesn't cause any parsing issues later on if researchers export this data to sync with external EEG or TMS systems. Thank you! Best, |
|
Hi @rmatsuda @thaismarchetti @LucasBetioli123 @vhemalheiro, I have received my GSoC decision, and while I am disappointed that my project proposal was not selected as a part of the GSoC Program, I am very interested in this project and really want to contribute to InVesalius. I would love to continue contributing to the project as a volunteer. I understand this won't be through the formal program, and I’m happy to work independently and submit Draft PRs for your feedback whenever you have a moment. I would really appreciate your support and the opportunity to contribute. Here is the link to my Google Drive with my initial proposal: https://drive.google.com/drive/folders/1T0vC1i4dawBHyEU2r5icUN0wGLYZ0Hsg Thank you so much, |
Uh oh!
There was an error while loading. Please reload this page.
Hi!
My name is Edison, and I am from the San Francisco Bay Area.
I am applying to GSoC 2026, and I am looking forward to contributing and collaborating with the community!
All reactions