Well not that so much as that you know e with if everybody ran fifty jobs at once then it would just bring everything to a halt and you know jobs would get delayed so sort of a sharing thing OK Um so you should try to limit it to somet sometim some number around ten jobs at a time Um So if you had a script for example that had a thousand things it needed to run um somehow need to put some logic in there if you were gonna use run command uh to only have ten of those going at a time And uh then when one of those finished fire off another one Um I remember I I forget whether it was when the Rutgers or or Hopkins workshop I remember one of the workshops I was at there were everybody was real excited cuz they got machines and there was some kind of like thing that sit sent things out So all people were sending things to all Yeah machines Yeah and things Yep were a lot less efficient than if just use your own machine Yeah exactly Yeah you have to be as a little recall bit but careful Hmm Um but uh you can also If you have that level of parallelization um and you don't wanna have to worry about writing the logic in in a Perl script to take care of that you can use um Just do and s you basically write a Make file that uh you know your final job depends on these one thousand things and when you run uh on your Make file you can give it the dash capital J and and then a number and that number represents how many uh machines to use at once Right then make sure that it never goes above that Right OK So I can get some documentation not systematically queued I mean all the jobs are running If you launch twenty jobs they are all running It depends Alright you Run command that I mentioned before is doesn't know about other things that you might be running So it would be possible to run a hundred run jobs at Right once and they wouldn't know about each other But if you use then it knows about all the jobs that it has to run and it can control uh how many it runs simultaneously So run command doesn't use or It uses export underlyingly But if you i meant to be run one job at a time So you could fire off a thousand of those and it doesn't know any one of those doesn't know about the other ones that are running So why would one use that rather than Well if you have um Like for example uh if you didn't wanna write a script and you just had a uh an HTK training job that you know is gonna take uh six hours to run and using uh the machine you typically use you can say run command and your HTK thing and find another machine the fastest currently available machine and and run your job there Now does it have the same sort of behavior as which is that you know if you run something on machine and they come in and hit a key then it Yes Yeah there are um Right So some of the machines at the institute um have this attribute called no evict And if you specify that in in one of your attribute lines then go to a machine which your job won't be evicted from But the machines that don't have that attribute if a job gets fired up on that which could be desktop machine and and they were at lunch they come back from lunch and they start typing on the console then your machine will get evicted your job will get evicted from their machine and be restarted on another machine Automatically So which can cause you to lose time right If you had a two hour job and it got halfway through and then somebody came back to their machine and it got evicted So If you don't want your job to run on a machine where it could be evicted then you give it the minus the attribute you know no evict and pick a machine that it can't be evicted from So Um what what about I remember always used to be an issue maybe not anymore that if you if something required if your machine required somebody hitting a key in order to evict things that are on it so you could work but if you were logged into it from home and you weren't hitting any keys cuz you were home Yeah I not sure how that works Uh Yeah seems like Andreas did something for that Hmm Um OK We can ask But sometime Yeah I don't know whether it monitors the keyboard or actually looks at the console TTY so maybe if you echoed something to the you know You probably dev wouldn't dev ordinarily console though something Yeah Right You probably wouldn't ordinarily I mean you sort of at home and trying to log in and it takes forever to even log you Yeah in and you yeah probably go screw this and Yeah You Yeah so know um yeah I I can not sure about that one yeah But uh OK Uh I need a little orientation about this environment and uh scr s how to run some jobs here because I never d did anything so far with this X emissions So I Um maybe ask you after the meeting Yeah Yeah and and also uh a Yeah really yeah good yeah resource for that if you can't OK sure Mmm Especially with regard to the Aurora stuff OK He he knows that stuff better than I do OK Well why don't we uh uh Sunil since haven't haven't been at one of these yet why don't yo you tell us up with you Wh what been up Um hopefully Yeah So uh shall I start from Well I don't know how may I how OK Uh I think start from the post uh Aurora submission maybe Yeah Uh yeah after the submission the what been working on mainly was to take take other s submissions and then over their system what they submitted because we didn't have any speech enhancement system in in ours So So I tried uh And u First I tried just LDA And then I found that uh I mean if if I combine it with LDA it gives improvement over theirs Uh Are y are you saying LDA Yeah LDA OK Yeah So just just the LDA filters I just plug in I just take the cepstral coefficients coming from their system and then plug in LDA on top of that But the LDA filter that I used was different from what we submitted in the