Participants
Retrospective
What went well?
- Material was prepared and tested beforehand
- Start the organization of the workshop early-on
- Half-day sessions were good
- Presentations were lean and easy to follow
- Positive feedback from JAO (ALMA Chile) participants
- Instructors were very active
- It was easy to check on group progress using Slack
- Motivation and participation of the audience
- Some experienced participants added interesting information during presentations
- All groups completed the minimum requirements for the practical session (Functionality Implementation)
What could be done better?
- Communication between instructors could have been better
- Some groups were not working together at the beginning
- The participants didn't know what was expected at several practical sessions
- The main integration server was not ideal and was hard to share the work being done with participants
- More time for the project tests and integrations
- Organization of the material
- Communication with participants could be better (goals/expectation)
- Organization, improvisation and consistency of the agenda
- The observatory demonstration (speaking more, showing both the screen and the telescope, explaining the debugging, etc.)
- The CDB repository confused some of the participants
- Virtual machine issues (Problems, not prepared by the partcipants, etc.)
What else can we do?
- Coffee break sessions to know other participants
- Have backup servers to run and connect to ACS
- Review the project (IDLs, communication, etc.)
- Improve documentation (ACS, Workshop, Project, Navigation, etc.)
- ACS workshop as a tutorial
- Invite experienced instructors
- Docker, Vagrant or other virtualization alternative
- REST API (Camera and Telescope + Simulation)
- Increase exercises or quizzes between presentations to improve engagement
- Create alternative projects for the workshop or for after workshop development
- Presentations, exercises as well as opening and closing words
- Improve CDB simulation (dummy image, telescope movement, etc.)
- Add CDB integration to Jenkins
not sure: The integration should be done for us through explanations /examples about. I mean with skeleton of the components header and soiurces pré built
What actions do we identify?
- Improve material
- Review IDL interfaces
- Change CDB repository and improve instructions
- Improve virtual machine
- Workshop agenda as a template in ACS space
- Investigate hardware alternatives or opportunities
- Improve ACS and Project documentation
- Motivate participants before the workshop (prepare and test VMs, etc.)
Results
Pain Points
- High priority
- Participants lost track of the expectations at several practical sessions
- Communication between instructors at some parts of the workshop
- Medium priority
- Material organization
- Members of a group working on their own
- Project demonstration (testing + integration)
- Late VM Preparation by some participants
Best Ideas
- High priotity
- Improve documentation (ACS, Workshop, Project, Navigation, etc.)
- Review the project (IDLs, communication, etc.)
- Coffee break sessions to know other participants
- Medium priority
- Increase exercises or quizzes between presentations to improve engagement
- Create alternative projects for the workshop or for after workshop development
- Docker, Vagrant or other virtualization alternative
Initial Actions
- High priority
- Workshop agenda as a template in ACS space
- Improve material (presentations, documentation, project, IDLs, etc.)
- Medium priority
- Investigate hardware alternatives for the workshop project
- Engage with participants in the weeks previous to the workshop
- Change CDB repository and improve instructions