📢 Project Presentation Update & Device Return Reminder
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 1/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- content
Research direction
This issue is an announcement about project presentations and returning devices, with no code files, tests, or requested repository change identified. There is no implementation work to start from or completion criterion to verify.
Written by the indexing model from the issue text.
Description
Yesterday, we had the project presentations from our first two groups, and they delivered an excellent performance—especially considering the very short preparation time.
Their teamwork, clarity, and technical execution were truly impressive, and they have set a high standard for the upcoming groups.
We would like to appreciate all team members for their dedication and professionalism.
Samuele Mattia Ferrari, @Samuele7F
Lorena Immacolata Crimenti, @lorenaimmacolatacrimenti
Mariapia Giulia Facchino, @mariapiafacchino
Roberto Lattanzi @blomius
Nour Alterri,
Hanine Djouad,
Nayab E Dur
Attached is a group photo from yesterday’s session so everyone can share in their achievement.
🔄 Device Return – Important
I kindly request all group leaders to return the devices by tomorrow, as we need to redistribute them to students in the Engineering Department for their scheduled activities.
🙏 Acknowledgments
A special thank you to Prof. @MarcoRianiUNIPR for taking this initiative forward.
And a huge thank you to Prof. @AldoCorbelliniUNIPR and Prof. @GianlucaMorelliUNIPR, who worked tirelessly behind the scenes to ensure the devices were ready for you.
We look forward to the upcoming presentations.
- Dominant language
- MATLAB
- Stars
- 30
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from UniprJRC/DSwithMATLAB
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
UniprJRC/DSwithMATLAB#243 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
UniprJRC/DSwithMATLAB#242 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
UniprJRC/DSwithMATLAB#241 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
UniprJRC/DSwithMATLAB#240 ·
-
Suggestion for the next edition
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
UniprJRC/DSwithMATLAB#238 · 2 comments ·
All issues in UniprJRC/DSwithMATLAB
Similar issues
-
bug priority: p3 size: xs
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Ax/Atb trim the caller's GpuIds in place, so blocksize-1 solvers run on one GPU after the first anglePossibly taken @AnderBiguri claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
mathworks/MATLAB-Coding-Guidelines#7 · 3 comments ·