• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

Seti 2 and Astropulse, arrangmant by me

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

Sir Ulli

Member
Joined
Oct 6, 2002
Location
Germany NRW
For all people who dont know BOINC or Astropulse, i write this litte arrangmant


The First:

Seti 2 will not be commerzial
BOINC is a Framework , and with this it will be able to go to ohther projects, but when a user
will crunch only for Seti and nothing else, he will crunch only for Seti 2, here
the Answer from Eric Heien from Berkeley

http://setiathome.ssl.berkeley.edu/bb/bb4/bboard.cgi?action=viewthread&num=1669

The first part from the new Boinc Framework is called

Astropulse

One of the first applications to make use of the new BOINC distributed computing framework is a project we call AstroPulse. This project will re-examine the existing SETI@home data tapes for a new type of signal radio pulses that only last for a microsecond.

This type of signal is different from those which would be caught by SETI@home. Since the pulses are so fast, they are broad-band signals. We need the full 2.5 MHz bandwidth for maximum sensitivity, whereas SETI@home breaks up this frequency band into 256 10 kHz sub-bands. Also, pulses travelling through the interstellar medium (the thin gas which fills the space between stars in our galaxy) become "dispersed," or stretched out in time. We can correct for this effect with a specialized algorithm (known as "coherent de-dispersion"), but it is very computation intensive, which is why this is a good distributed computing project.

There are several possible sources for this type of signal. One possible source which is already known is called a pulsar. This is a rapidly spinning neutron star which "beams" radiation at us every time it rotates. Our search may uncover new pulsars, since no one has looked for pulses this fast before. Another possibility is extraterrestrial civilizations - a series of pulses could be an easily recognized signal, and a pulse with negative dispersion would stand out as obviously artificial (natural dispersion always causes faster frequencies to arrive first). A third possibility is an evaporating black hole. It has been theorized that a black hole which completely evaporates will give out a short radio pulse at the end of its life, but no one has seen this happen yet. Our search will be at least 100 times more sensitive than previous efforts.

We are well on our way to an in-lab test of the AstroPulse/BOINC system. A beta version will be done by the end of 2002, and public release should follow early in 2003.


The second:

Seti and cheaten
By Seti 2 there will be a Result verification, and Credit will not be given, until the results
have been verified. Written from Matt Lebofsky from Berkeley

http://setiathome.ssl.berkeley.edu/bb/bb2/bboard.cgi?action=display&num=11716

The Third:

The Telescope in Arecibo will be able to scan only one third ore one of three parts of the Air for
information to search, but only in the north of the hemisphere.
But someone will thougt there is someting in the south?
The new Telescope at Parkes Observatorium in Australia, the biggest Radio Telescope at
the world will be able to look in the south hemisphere.And the people there have agreed
to work with Berkeley to find ET.

The Work at the new Telescope are in good progress, and the Telescope is able to look
at Data at 13 different Air Positions, this ist 13 multiplied to the Arecibo Telescope.


Something about the Stats with Seti 2

I thougt that the Stats are going and each Team is going from zero

http://boinc.ssl.berkeley.edu/credit.html

Each project gives you credit for the computations your computers performs for the project. These credits are used to generate web-site "leaderboards" showing individuals, teams, and categories (countries, CPU types, etc.) ranked by credit.

BOINC's credit system is based on a "reference computer" that does

1 billion floating-point multiply/adds per second
1 billion integer multiply/adds per second
4 billion bytes per second of traffic to and from main memory (sequential, half reads and half writes)
BOINC's unit of credit, the Cobblestone, is one day of CPU time on the reference computer. (Credit should ideally reflect network transfer and disk storage as well as computation. But it's hard to verify these activities, so for now they aren't included.)
Each project maintains two types of credit:

Total credit: The total number of Cobblestones performed.
Recent average credit: The average number of Cobblestones per day performed recently. This average decreases by a factor of two every week.
Both types of credit (total and recent average) are maintained for each user and host.


btw what is a Cobblestone

and something about joining a Team

http://boinc.ssl.berkeley.edu/account.html

You can join a BOINC project as follows:
Visit the project's web site and create an account. This involves filling out a form with
An email address.
A public "screen name" (real name or nickname).
Country (optional)
Postal Code (optional)
You will receive an email containing an account key (a long random string).
Download and install the BOINC client program. It will ask for a project URL and an account key. Enter the project's URL, cut and paste the account key from the email.
That's it! You can go to the project web site to set your user preferences.
Multiple hosts under one account
You can run BOINC on many hosts, all under one account. Once you have created an account as above, you can add new hosts in either of two ways:
Download and install the BOINC client program on each host, and cut and paste the project URL and account ID as above.
If the new host is the same type as an existing host, copy the contents of the BOINC installation directory from an existing host to the new host.
The BOINC client resides in a BOINC home directory. If hosts share a network file system, each host must have its own BOINC home directory.


and someting about Sub-Teams, here

http://boinc.ssl.berkeley.edu/teams.html

Teams
Participants in a project can form teams. Each participant can belong to at most one team. The participant who created the team is called its founder.
A team is local to a project. There is currently no provision for teams that span projects.
Total and average credit is accounted for teams; a team's credit is the sum of the credits of its members.
A team has the following attributes:
A textual name.
An HTML name (can include graphics).
A textual description.
An optional URL (e.g., of the team's web site)
A type (business, school, club, etc.).
The founder.
A list of members.
A project's web site lets you:
See lists of the teams with the most credit.
Search for teams in various ways.
Join a team
Quit your current team
The founder of a team has some additional capabilities:
Edit the team's attributes.
View the email addresses of all team members.
Remove members from the team.
Disband the team


and something about the Preferences, here

http://boinc.ssl.berkeley.edu/prefs.html

You can specify preferences determining and limiting how BOINC uses your computers. Preferences are divided into two groups:
Global preferences
Global preferences apply to all projects in which you participate. They include:
Whether work (computation and network transfer) should be done while the host is being used (i.e. during keyboard and mouse input).
Whether work should be done while the computer is being powered by batteries (for laptop users).
Whether to wait for user confirmation before making network connections.
Min and max days of work to keep on disk. If the host is frequently disconnected from the Internet, the min should be at least as long as the typical period of disconnection. The larger the difference between min and max, the less often the BOINC client will connect to the Internet.
Maximum disk space used by BOINC.
Maximum percentage of free space used by BOINC.
Minimum disk space to keep free.
You can view and edit your global preferences through a web interface, at the site of any project in which you participate. Changes are automatically propagated to all your hosts; this is done the next time the host contacts the project's server, so there may be some delay.
Per-project preferences
There is a separate set of per-project preferences for each project in which you participate. They include:
Resource share: if projects contend for resources, the amount allocated to a project is proportional to this number.
Whether to show email address on web site
Whether project should send emails to user
Project-specific preferences (defined by the project; e.g., to specify graphics color schemes).
You can view and edit per-project preferences through a web interface at the project's web site

and something of the beginns, i thought Summer 2003, because the Beta Test is going on
in the Februar 2003, written in the SAH Forum here

http://setiathome.ssl.berkeley.edu/bb/bb2/bboard.cgi?action=viewthread&num=16609

So thats all at the Moment, and remember Englisch is not my first Language, so if there
are errors please forgive me.


to be continued......

with best regards
Sire Ulli
 
Back