The '&' method on itself doesn't prevent the assembly process being killed on disconnect (at least not on the AWS I tried it on). We have previously used screen in a similar course (https://aschuerch.github.io/MolecularEpidemiology_AnalysisWGS/07-getting-data/index.html). I added a similar description of screen, to make sure some kind of connection-issue proofing is done.
Sorry for the big change, I realise it adds an abstract concept to the lesson. However, I think the time investment in learning this is not very large compared to the '&' method. Especially considering the '&' method doesn't seem to reach the goal of ensuring the process isn't killed when disconnecting (at least on the AWS instances we'll be using this week for this course).
I'll be teaching this lesson on Friday so I'm happy to see how much it adds time-wise to the lesson.
The '&' method on itself doesn't prevent the assembly process being killed on disconnect (at least not on the AWS I tried it on). We have previously used screen in a similar course (https://aschuerch.github.io/MolecularEpidemiology_AnalysisWGS/07-getting-data/index.html). I added a similar description of screen, to make sure some kind of connection-issue proofing is done.
Sorry for the big change, I realise it adds an abstract concept to the lesson. However, I think the time investment in learning this is not very large compared to the '&' method. Especially considering the '&' method doesn't seem to reach the goal of ensuring the process isn't killed when disconnecting (at least on the AWS instances we'll be using this week for this course).
I'll be teaching this lesson on Friday so I'm happy to see how much it adds time-wise to the lesson.