I really don't like the GUI version of SETI@Home for BOINC.
When will the command-line version be available for download?

> I really don't like the GUI version of SETI@Home for BOINC.
> When will the command-line version be available for download?
>
I wouldn't look for it before they get alot of the current problems behind them. The command line version will probably be faster, as it is with Seti Classic, so will make the problem of not enough units worse.
Have you thought of just going back to Seti Classic during the problems with Boinc? The rumor is we are now processing only "interesting" results, meaning ones that have been returned with things that make them "interesting" enough to be rechecked for whatever.

> I wouldn't look for it before they get alot of the current problems behind
> them. The command line version will probably be faster, as it is with Seti
> Classic, so will make the problem of not enough units worse.
> Have you thought of just going back to Seti Classic during the problems with
> Boinc? The rumor is we are now processing only "interesting" results, meaning
> ones that have been returned with things that make them "interesting" enough
> to be rechecked for whatever.

They said they would abandon the SETI@Home classic after the new one is stable enough, so I won't use the classic one anymore.
If the BOINC version only process "interesting" results, then there should be only a small amount of unprocessed WUs and soon the classic one be abandoned.

The command line version is already included with BOINC, but it doesn't work with the GUI properly yet so if you use the CLI, you can't really use the GUI to check the progress or things can get messed up.

The CLI version is also not any faster than the GUI. That's basically because BOINC doesn't process the SETI workunit. BOINC runs a program very similar to the CLI version of Classic in the background, so the SETI core program by default loses the bare minimum amount of CPU cycles to graphics and any general Windows overhead, and BOINC just sits there unless it's uploading or downloading or you tell it to do something specifically. If you are going to use the CLI exclusively (no GUI whatsoever), you should also know that the CLI has a command line switch to allow it to be installed as a WinNT/XP/2k service.

The CLI is located in the BOINC directory and is called "boinc_cli.exe" and "-install" is the switch to insall it as a service. Just remember that running the GUI and CLI simultaneously (for now) causes problems.

Chris

> > I really don't like the GUI version of SETI@Home for BOINC.
> > When will the command-line version be available for download?
> >
> I wouldn't look for it before they get alot of the current problems behind
> them. The command line version will probably be faster, as it is with Seti
> Classic, so will make the problem of not enough units worse.
> Have you thought of just going back to Seti Classic during the problems with
> Boinc? The rumor is we are now processing only "interesting" results, meaning
> ones that have been returned with things that make them "interesting" enough
> to be rechecked for whatever.
>

>
> They said they would abandon the SETI@Home classic after the new one is stable
> enough, so I won't use the classic one anymore.
> If the BOINC version only process "interesting" results, then there should be
> only a small amount of unprocessed WUs and soon the classic one be abandoned.
>
Sorry I wasn't clear, Seti Classic is only processing "interesting" units, Boinc is doing new work on old units. Boinc has a whole new algorithym in it so all the old units can now be reprocessed for things we didn't know how to look for before! We do that almost everytime a new version of the software comes out.
Boinc is having growing pains right now and it could be awhile before Classic is abandoned. I have no idea how long "awhile" is! But unless they decide to close it and use the hardware for Boinc I would guess it could take "awhile".