Feedback from sticky notes - StAResComp/2018-12-10-standrews GitHub Wiki
Room 1
Monday AM: The Unix Shell (Paddy McCann)
Green Notes
Generally good pace to follow
Exercises useful
This was well explained
Instructions were easy to follow
Well paced delivery
Nice introduction
Nice idea with the green/red papers
Computers are great
Really satisfying when you manage to do something and can apply it 🙂 (I am bad at computers)
Enjoyed working along with explanations
Well explained
Game me back my memories on how to use prompt
Easy to follow
Nice intro to Unix shell
Everyone very knowledgeable
Brushed up on my old Unix skills + learnt some new commands
Like how you went through the usage in parallel
The explanation is well combined with the practical examples
Have exercises to test the skills learnt during the lecture
Interesting once it got going
Useful at the end
Post its are fun
The lesson was well paced + delivered and was interesting to a complete beginner
I like Michael's notes on the white board - those were very helpful
Very well explained.
Good ratio of demonstrators to students
Interesting
Maybe useful
Pink Notes
The practical applications weren't very clear
Too slow at start, little bit rushed at end
Sometimes the purpose of commands wasn't fully explained
A glossary in front of us with all the commands would be useful
I didn't really know what the code bit meant
List of terms and definitions would be helpful
Switching between windows distracting
If you fell behind it was easy to get lost
A bit fast paced
Hard to relate what the commands meant
Too many information for only one morning
Not enough time to familiarise with all the commands
Tell people to shut-up + listen!
Moving from nano too quickly meant I couldn't type all the content (keep on screen somehow)
Took me a sec to understand words like "argument" and other technical stuff
Too slow at start
Too fast at end
We need more biscuits
A bit too much info after break. Would rather have done less but with more time to digest it
Exercise web page was a little confusing to follow during lecture
It was easy to fall behind if we got stuck and miss explanations of what symbols/commands do. This could be helped if the handout was a little more complete e.g. explain head, tail, $ etc.
Thank you. I thought it went a little fast at times but mostly I could follow OK with the aid of the helpers
Monday PM: Python 1 (Michael Torpey)
Green notes
generally well run and delivered
nice to see how the logic of it all comes through
entertaining and engaging lecture.
Good pace, very clear, entertaining.
nice lecturer, pretty engaging style
It was good
Interactive lecture, easy to follow
nicely explained
Very thorough! =] enjoyed it. especially graph plotting.
Good interactions. Very entertaining
Well delivered
Mostly well explained and at a good level
Enthusiastic & funny, Easy to follow
Pink notes
I would have liked to have link to resources where I can advance my knowledge.
Maybe a bit too much 'jumping' between topics
Felt a bit long
not much time to practise on a code
Glossary of all the commands we are using would be helpful
maybe a little [text unclear]
More classic Dad-jokes please Michael.
Meanings of all commands in longer codes could be more fully explained
Maybe explain where it would be useful to use python over excel (i.e in context of making graphs etc.)
I couldnt remember all the various commands eg numpy.plot.something - is there a list of them somewhere?
Tuesday AM: Version Control with Git (Paddy McCann)
Green Notes
Well presented
Useful
Commands used clear to follow
Good pacing
Work in collaboration
The collaboration exercise was fun and interesting
It was great! Thank you.
Was well explained and easy to follow.
All very interesting. Thanks.
Really useful general introduction to git.
Exercises and collaboration tasks
The demonstrations were very helpful
Useful
Good practice in the stuff
I liked the analogies used like 'git add' being getting people together for a photo and 'commit' being like the snapshot, more like this would be great!
Really fun, I learned loads
Great session
Good basics, covers the reasons why I should use this in the future
Interactive/collaboration was good
Pink Notes
Too slow. Maybe consider classes at differing levels.
Application of version control/collaboration could be explained more
The beginning was a bit slow
Nothing really. Thank you.
I was confused about the general point of doing it at the beginning
A general introduction of what git would be useful for [presumably meaning that they felt this was missing? - PM]
Maybe a workshop style would have been better than a presentation
Too long
Not enough of a break
Confusing towards the end
Tuesday PM: Python 2 (Michael Torpey)
Green notes
Fun afternoon! Useful to see how to transfer script out of jupyter!
Very interesting. Thanks!
Graphs - awesome!
Thank you Michael, your lesson was very clear & interactive. I enjoyed it.
Nice to see everything we learned coming together - I enjoyed making our own functions
all good!
Learning about python with an example was very useful
Great lecture, great enthusiasm, great patience. I learned a lot. Thank you!
Up to write the fuction + code in phytom [sic]
Nice teachers
The functions (command?) on the white board was good to refer to.
Very nice, good teachers. Good [text unclear], best advance workshop for the CRITICAT since at least 2015!
Good Appreciation of the possibities of writing scripts etc.
Excellent workshop. Esp. Michael <3
Pink notes
Slow paced if you are familiar with Python
Not always easy to understand what to do in the examples
Vegan lunch wasn't very good.
We had some errors trying to run our final python script using Git Bash but there wasn't much time to fix them.
not very much. Thanks
Example with mean avg function... missed the math
maybe asking us to write a function was too difficult?
More info on further stuff we can find to learn more but tbh I have nothing negative to say - it was really great :)
might be good to alternate on day 2, eg
day 1 unix AM + python PM
day 2 python AM + unix PM
just coz people + laptops flagging by end of day and seems a shame for python to miss out on full attention both days
Having a session on how to plot nice graphs would have been useful!
Room 2
Monday AM: Python (Olexandr Konovalov)
Green notes
useful to learn how to use Python
increased awareness of the possibilities of using Jupyter
good introduction to basic commands
good introduction, easy enough to follow
very good overview of basic tasks to get started
useful: good introduction to python; good help from helpers
having the helpers to keep you on track
going through basics and making sure everyone is up to speed with what was going on
got an appreciation of how to program and learned some terminology
learning how to process data quickly
learning the concept of 'strings' [unclear]
far greater understand of Python language
loops and arrays
for loops
loops
slicing
plot, loop commands => very useful
plot graphs of big databases
arranging figures in efficient way [unclear]
liked plotting graphs
graphs
graphs
Orange notes
purpose of python
why it is applicable to research
could be improved: application of python -> what can this be used for
applications of using these techniques
maybe more of a goal -> analyse data
perhaps show the data beforehand so we can see how it works
more practised based examples
the workshop was a bit too fast at times
bit too fast on screen especially when you are reading help + are lost
how to transfer this to programs
applications of loops
range + loop - I am not comfortable programming solo yet
how to tell the system to search for an element in loop
some terms still confusing
more features of pyplot. Exporting charts?
make graphs from whatever data
explain the syntax not so fast please
the logic behind when to use commas, brackets, spaces etc.
spend more time explaining why to add characters such as ( or [ at beginning
I now have a greater understanding of how I might apply Python to manipulate data
learning to write short lines of code was really rewarding
morning session was much better paced today - spending more time on explanations allowed me to learn more!
the morning session was more relaxed and seemed useful. I can use it for my work.
pace and design of morning session worked very well for developing understanding
feel more confident expressing what I studied.
good doing exercises independently to put into practice what we have learnt
exercise to do by ourselves with functions more useful to actually try by ourselves
the exercises from today were really interesting
exercises were good, if possible do more of these
I like the way in which Python can simplify analysis among a very wide number of data
good interactive problems before lunch
files handling and plotting
like working through examples
helpers get you back on track quickly! :)
good help when we need
Pink notes
Pace quite fast, which makes it hard to write and understand
I think it is necessary to give a general background before starting working on the bash platform, otherwise it is very difficult to follow
Pace too fast overall but post-lunch it was so fast I didn't follow
Bad: last section was very fast and hard to follow; Explain why each element of the coding is needed
It is sometimes hard to copy doe at a fast speed and understand what you are writing; Spend more time explaining? I understand we don't have much time/it feels a rush
Lots of people saving the initial files in the wrong place caused trouble
It was hard to follow the Python half-hour session without any real interaction
The last Python thing in the terminal prompt was beyond me
Afternoon session was way to quick and following but not doing was very difficult
I still don't feel comfortable approaching Python without the use of the Jupyter notebook
Nothing bad to say
print(fence('name','*') original + wrapper
Rushed explanation past lunch
Sometimes a little bite too fast
Too fast at times
Too fast
Tuesday PM: Version Control with Git (Paddy McCann)
Green Notes
Good pace
Followed afternoon session well and was able to make the bio entry (unfortunately wifi problems restricted me from completing rest of lesson)
Good, clear to follow content
Good pacing
Clear instructions
Quite interactive workshop
Good overview of what can be done in Git
Generating conflicts in the code was a very good way of getting an understanding of how the code actually works/how to work with it
Conflict 😉
Tone & pace very easy to follow, very easy to understand
Had good fun with conflict section
Again like trying ourselves with exercises to get the hang of it
Good:
Delivery of lesson was good - good pace
More interesting in applications i.e. modifying other people's files etc.
Went at a nice pace, was easy to follow & explained all steps
Most interesting part
Very well delivered, clear explanations
Very helpful people running the workshop
GitHub is very good for track change in our files
Fully aware of advantages & would attempt to use GitHub to collaborate
Not too fast this afternoon + good help
Pink Notes
Pace of the workshop could be improved + collaboration part was confusing
The links to the online learning source could be better emphasised, didn't know where to find it
At some points can get confusing and easy to get lost
A bit slow in places
Session went really well, it was only disappointing we didn't have more time
Can't think of anything bad this session
Not sure what the use of writing in GitHub is. Are you really going to write a paper in it?
Hard to put it in context related to chemistry data
Bad: uses? Google docs can do just the same etc.
Other applications?
Creation and importing of multiple files irritating
Explain better how the shared directory works during the making changes process at the same time