VLAR bat |
![]() |
| log in |
Message boards : Number crunching : VLAR bat
1 · 2 · Next
| Author | Message |
|---|---|
|
Hi, | |
| ID: 847440 · | |
|
Someone posted the batch-codelines here at the forum. findstr /n "<true_angle_range>0\.[0-1]" D:\boinc_data\projects\setiathome.berkeley.edu\*.* > low_ar.txt findstr /n "<true_angle_range>0\.[2-9] <true_angle_range>1\.[0-1]" D:\boinc_data\projects\setiathome.berkeley.edu\*.* > medium_ar.txt findstr /n "<true_angle_range>1\.[2-9] <true_angle_range>[2-9]\.[0-9] <true_angle_range>[1-9][0-9]\.[0-9]" D:\boinc_data\projects\setiathome.berkeley.edu\*.* > high_ar.txt ____________ | |
| ID: 847449 · | |
|
yes, I tried that one too. Made the changes to reflect my OS, but didn't work either. Probably would work for me if I had Vista. | |
| ID: 847451 · | |
|
find <> findstr | |
| ID: 847452 · | |
|
Ok, thanks, I made that change. Will see what happens, apparently I don't have any ATM | |
| ID: 847453 · | |
Ok, thanks, I made that change. Will see what happens, apparently I don't have any ATM FINDSTR is more useful than FIND since it does not output names of files that do not contain the searched-for string. I think the problem lies in the spaces included in the path to your data files. So this should work better: findstr /n "<true_angle_range>0.00" "C:\Documents and Settings\All Users\Application Data\BOINC\projects\setiathome.berkeley.edu\*.*" > vlarfound.txt Note the extra quotes round the file path. Right-clicking on the output text file and "Open-with" Wordpad makes it much easier to read, especially if you set Wordpad to "no-wrap". Hope this helps. F. ____________ | |
| ID: 847455 · | |
Ok, thanks, I made that change. Will see what happens, apparently I don't have any ATM That helped immensely, and has spotted the VLAR for me finally. I appreciate letting me know what the problem was in mine so I can avoid such errors on my part in the future. Thanks for your help Fred W and Maik. I'm a happy camper now. ____________ | |
| ID: 847530 · | |
That helped immensely, and has spotted the VLAR for me finally. I appreciate letting me know what the problem was in mine so I can avoid such errors on my part in the future. No problemo. Glad to be of service. And here's a variant that may be of interest:
@echo off
echo VLAR Tasks found:
echo.
findstr /M "<true_angle_range>0.00" "C:\Documents and Settings\All Users\Application Data\BOINC\projects\setiathome.berkeley.edu\*.*" > con:
echo.
echo Done.
pause 0
If you save the text to a file on your desktop with a .bat extension, then you can double-click on the icon and it will list the offending files in the cmd window that it opens. When you have identified and aborted the files, return the focus to the cmd window and press any key (other than Shift, Alt, or Ctrl) and the cmd window will close. No need for a .txt file at all. F. ____________ | |
| ID: 847866 · | |
|
Hi, | |
| ID: 847997 · | |
Hi, In the one that outputs to the console (con:), the /m is more useful than the /n. For some reason that I haven't figured out, with /n, the output of the angle range to con: is in invisible text as is any text following the file name of the last one found. The /m forces it to output the file name only which gives a tidier output in the cmd window. F. ____________ | |
| ID: 848114 · | |
|
Yep, good point. Much easier to see using m for the first batch file example. Using n on the second example with multiple AR gives me the AR included with the WU in the text file, where m doesn't. | |
| ID: 848133 · | |
Yep, good point. Much easier to see using m for the first batch file example. Using n on the second example with multiple AR gives me the AR included with the WU in the text file, where m doesn't. One other point (since I am still waiting for the traffic to die down so I can report my results). If your preference is for the .txt file output, you can get the batch file to automatically open one of the output files in wordpad when it is done. You have to find the full path to wordpad.exe on your machine (on my XP laptop it is C:\Program Files\Windows NT\Accessories\wordpad.exe). If you want to look at your low_ar.txt file then, using my wordpad.exe location as an example, just add the following line to the end of your version of Maik's .bat file: Call "C:\Program Files\Windows NT\Accessories\wordpad.exe" low_ar.txt F. ____________ | |
| ID: 848145 · | |
... version of Maik's .bat file ... To be correctly it isnt my batch-file. Some other user posted it but i wasnt able to find the post ;) ____________ | |
| ID: 848151 · | |
|
I'd already decided to use the version of the one you created without the text file the most. It has the info I need to know about which VLAR tasks to abort, and is one step. That works well for me :) my desktop is cluttered enough. | |
| ID: 848155 · | |
Yeah, Notepad for writing, Wordpad for reading - me too. Comes with long experience. And no worries, still crunching away. I still have 15 AP's unstarted in my cache as well as many MB's. The AP's alone will take 50+ hours to get through on the 3 cores I have devoted to S@H. F. ____________ | |
| ID: 848174 · | |
|
I found this batch-file in this forum thread on Seti Beta | |
| ID: 848188 · | |
|
Got a lot of VeryLowAngelRange WU's since server-crashed ... I found this batch-file in this forum thread on Seti Beta Tanks Kevin, thats the one who posted it first ^^ : Alexander Klietz ____________ | |
| ID: 848195 · | |
I ditched both and replaced it by Notepad+, it doesn't crash on large files, tabbed screens, and I think it handles Unix/Mac line endings too. You could easily go one step further with the multitude of free syntax highlighting editors useful for things like XML editing. ____________ | |
| ID: 849149 · | |
I found Metapad as well, less features but still much better then notepad and wordpad and a smaller footprint too ..@110k vs @430k. ____________ HAY! Watch this! LLLLEEEEEERRRROOOOOYYYYY! ...yikes... | |
| ID: 849813 · | |
Yep, good point. Much easier to see using m for the first batch file example. Using n on the second example with multiple AR gives me the AR included with the WU in the text file, where m doesn't. and what you do with this WU in "low_ar.txt", abort them? | |
| ID: 853479 · | |
Message boards : Number crunching : VLAR bat
| Copyright © 2013 University of California |