Why does head -1 *.pdb ...produce the file name but when you do what amounts to the exact same command in a loop for file in *.pdb; do head -1 $file; done ...the file name does not appear? This doesn't make sense.
So I typed in the exact command described around 7:20-using a working directory with .txt files in it-and it didn't work at all. Instead, I got: wc: find: open: No such file or directory wc: .: read: Is a directory wc: -name: open: No such file or directory wc: *.txt: open: No such file or directory 0 total There does not appear to be any distinction between "back quotes" and normal quotes on my computer though, so is that the problem?
Also, super annoying that he doesn't just tell us what the commands tail, split, cut, uniq, <, and ? do. It takes a long time to look these up individually if you don't know what you're doing (i.e. everyone who's watching this), whereas it would be super quick to learn if he just briefly ran through them.
stdin and stdout don't seem to be explained well. It seems like he says that stdin is, by default, "whatever we type in" and that stdout is, by default, to print whatever the output of the program is. But then for the command [wc -l *.pdb > lengths] he says, "Since we've provided some file names as arguments, wc read from them instead of standard input." If standard input is "whatever we type," then how are file names that we typed an alternative that is read "instead of standard input"? This makes no sense to me.
Thank you for making this. This video makes it so much easier to understand while learning TOP. I know the video is old but the information is still the same to this day.
This is great material thanks with a lot of historical references, the name of the trainer/lecturer should be made available for reference.citation, thanks although I can reuse the material under cc, I want to use the name of the trainer in my citation
11 years after this person saying that it is a some what out-of-fashion topic, i find this topic critical to work work with my TUI setup. This is an absolute gem.
It's not very often that I look for the solution to a problem and actually find something that discusses exactly the problem I have, but this video does just that :-) I am building an astrophotography weather monitoring station, which checks wind, rain, temperature, humidity and how good the 'seeing' is, which then will send me an SMS if things look good for an astrophotography sesssion. I tried to implement the star counting algorithm you put forward here on an ESP32-CAM module, and was having all sorts of problems with the code crashing during the recurison, then I engaged my brain and added some debug code and found that the issue is that your suggested approach results in an infinite recursion, as processing a BLACK pixel at x, y, then calls the Fill function for (x-1, y), (x+1, y), (x, y-1) and (x, y+1) (excluding edge cases), but calling Fill with the first set of prarameters, then wants to do a fill on the x, y pixel we're already pointing at, then round and round we go, LOL. As we will have already processed the pixels above and to the left of the current pixel, we do not need the code that calls fill for (x-1, y) and (x, y-1). Removing the two if statements that potentially call Fill with x-1 or y-1 sorted me out straight away! Many thanks for providing the groundwork though!
Hello, thank you for sharing this. Would you happen to have a more descriptive example of a file system, for instance, one that is actually on your system? Perhaps you could share screenshots of the system.
Man, You clearly know what you're doing, but(!), the tone of your voice, and intonation, makes one wanna go somewhere, and step of a bridge in a profound depression, or something like that!
at 1:50 "MPI is a standard library for message passing" that statement is wrong. MPI is not a library at all, it is an interface specification and libraries are made from that specification, an example being openMPI
