If you are doing a fyp or masters project with me, here are some general instructions.
I'm terrible with paperwork. And buried in email and multiple research projects. You need to make sure we have regular (weekly) meetings (possibly online), things happen before deadlines, forms get signed and filed, reports get turned in, I know what you're doing, etc. When you need something from me, you might have to hunt me down like a wild animal. If you need something technical and it would be better right away than waiting until a regular meeting, that's fine: just email or call, I really don't mind. In this vein, if you want me to read or edit or test things, you need to (1) get them to me and (2) sit on me until I do it.
It's your project. Not mine. Yours. You're responsible for making it a successful project that you're proud of. You. I'm very happy to help. I'll give advice, which you're free to ignore. But keep in mind: I'm your faculty advisor, not your project manager. If your project slips deadlines and you have zilch to show when it's due, you'll be in trouble, and I'll be sympathetic.
I'll make a project git repo on gitlab.cs.nuim.ie that the two of us have access to. If you need help getting set up with it, or using git, see below, and ask for help as necessary. If you don't know how to use git so you work outside it for a while thinking you'll get up to speed on it later and fix things up YOU WILL REGRET IT. Trust me on this. Do not do that. See below.
Please please please PLEASE PLEASE PLEASE PLEASE do everything in git. Including not just code, but also all your notes, and other paperwork like reports. And right away, make a plain text NOTES file where you put simple things, like “need to decide on a framework to build this in, looked at FOO which has problem X and at BAR which has problem Y so forget about them.” Git commit that. Push. Every time you scratch your nose while thinking about the project, add a line to that file and commit it. (No need to even date the entries, you can see that with "git blame".) If you do this, when it comes time to write your project report, you will be very happy.
Also, if you put stuff into the git repo that doesn't belong, don't worry: we can rewrite history later. I'm happy to show you how. Better to add stuff that doesn't belong than to not add stuff that does. You can use "git lfs" for binary blobs and downloaded data files and such; if you don't know how, ask and I'll show you.
First, you need to have git and ssh installed on your own computer.
You need an ssh key; if you don't already have one you need to generate it. That key has two files, a private one with a name like id_rsa and a public one with a name like id_rsa.pub. The public one is what you upload. (Yes, you can forget ssh and use an https authentication token instead if you want.)
Basically you need to do
git clone ssh://git@gitlab.cs.nuim.ie/PATH/REPO.git
But for that to work, you need to register your SSH public key on the web site.
Browse to https://gitlab.cs.nuim.ie and log in.
Click on "edit profile" which is the circle on the upper right of the sidebar on the left.
Click on the SSH Keys tab on the left.
Click on "Add new key".
Upload your public ssh key.
git clone
or
browse there and click "Help" in the lower left corner, then "Use GitLab" or "New to Git and GitLab" or whatever, depending on what you know.
If you have trouble let me know and we can share screens and I'll walk you through it.
Then you need to actually use it. Religiously.