Aus SETI.Germany Wiki
(Weitergeleitet von Pirates)
Ursprünglich Testprojekt, um bei der Entwicklung von Projektsoftware (Bildschirmschoner von Einstein@Home) zu helfen. Momentan beteiligt sich Pirates@Home an dem Projekt Interactions in Understanding the Universe (I2U2) welches Lehrern und Schülern den Zugang zu und die Nutzung von LIGO - Daten ermöglichen soll.
Pirates@Home ist eines der Testprojekte für bzw. unter BOINC. Allerdings eines der sinnvollsten.
Die momentane Entwicklung bei Pirates dient dazu, BOINC daraufhin zu testen, ob, wie weit, oder mit welchen Modifikationen es zur Vernetzung wissenschaftlicher Schul-, Highschool- und Uni-Arbeit/-Projekte dienen kann.
Weiterhin testet Pirates ständig die Entwicklung neuer Features für die BOINC-Forensoftware. Und das schönste ist, dass Pirates immer mal wieder neue Screensaver ausprobiert. Unter anderem ist der Screensaver von Einstein@Home von Pirates entwickelt worden. Dies ist der Part zu dem eigentlich WUs bei Pirates generiert werden.
Auch hat Pirates letzthin eine Einbindung einer Wiki direkt zu einem Projekt erfolgreich getestet.
Primär ist der Sinn einer Unterstützung von Pirates@home also eigentlich nicht, massenweise WUs zu crunchen, sondern eher im Forum zu lesen, die Wiki auszuprobieren, und zu schreiben, wenn man Ideen, Wünsche oder Fehler entdeckt hat. Aber natürlich auch WUs zu rechnen und wenn möglich die Performance der Screensaver zu betrachten. Und wenn hier Probleme auftreten, dies zu posten.
Unsere SG Piratencrew macht aber natürlich beides: Helfen bei der Fehlersuche und beim Nachdenken über Features aber natürlich auch crunch ... crunch ... crunch ... Goldcredits scheffeln und horten!
Und das coolste dabei ist: Piraten haben Spaß bei der Arbeit!
Im Forum gibt es ein eigenes Unterforum zu Pirates mit verschiedenen Threads zur Performance-Optimierung, allgemein zum Projekt und zu verschiedenen weiteren Aspekten. Pirates im SETI.Germany-Forum
Bei Pirates gibt es momentan fünf verschiedene Applikationen:
Optimierung der Piratenschiffe!
Pirates-WUs sind immer knapp und meistens gar nicht verfügbar. Im Gegensatz zu anderen Projekten kommt es nicht darauf an Wus möglichst schnell zu berechnen, sondern möglichst viele zugeteilt zu bekommen. Um das zu erreichen gibt es ein paar Tipps.
[bearbeiten] Test Features
One of the purposes of Pirates is to try out modifications to the BOINC software. When a feature is found which we think should be a part of BOINC then we submit the modification to the developers for possible inclusion in the main BOINC code base.
[bearbeiten] Current Modifications
This is a list of current modifications to BOINC which are being tested here. The items which are struck through by a line have been submitted to the BOINC developers and will appear in a future release of the core (or are already there).
[bearbeiten] Mark thread as read
a forum thread can be marked as having been read simply by clicking on the "new content" icon, without having to visit the thread
[bearbeiten] Cached page autorefresh
cached pages can optionally be set to automatically refresh after a given time, specified in proportion to the cache interval. For example, on Pirates@Home the status page is cached, and so it can only be updated after 10 minutes. The optional second parameter to the start_cache() function is 2.0, so the page will automatically refresh itself after 20 minutes.
when someone replies to a forum posting the previous article is enclosed in tags [TRIM_THIS_quote] rather than [quote], and by default anything within such quotes is removed from the posting. This forces the writer to edit the tags, and hopefully they will trim the quoted text at the same time.
[bearbeiten] Quote attribution
When replying to an earlier posting, the [quote] tag becomes [quote=name], which shows up in the posting as "Name wrote:...". This has always worked, but the reply script did not automatically insert the name of the person quoted. Now it does.
[bearbeiten] Customized user identification
A project may create its own custom function project_forum_user_info($user) to display user information under their avatar in the forums. Example: show country and team.
[bearbeiten] Private forums
Some forums or categories are only readable by authenticated participants
[bearbeiten] Signature block size
The size of the signature block is limited to a height of 100px to prevent huge signatures. In the past we tried limiting signatures to only one image, but this seems to be the better way to control large signatures.
[bearbeiten] Blockquote CSS fix
Change the CSS so that the blockquote style used by the forums is only used in the forums, not by every blockquote tag on the site.
[bearbeiten] Limited rating points
Users have a limited number of rating points, which they can use to rate postings or profiles. The maximum number is configurable (5 seems to work well). Points are slowly added back over time (1 per 8 hours seems to work well, but this is also configurable).
[bearbeiten] User management page
This control panel page allows a project administrator to see details about a user, easily change their special_user bits, and easily suspend posting privleges or revoke a suspension. File: html/ops/manage_user.php. For an administrator, the red x-box is a link to this page, not the page to report abuse.
[bearbeiten] Help Desk - recent questions
the Help Desk area only shows recent questions and replies (where recent is configurable - we've tried 3-7 days) so that it remains "fresh"
[bearbeiten] Forum „attic“
Discussion rooms (forums) which are no longer used are put "in the attic" by making their orderID negative. They still exist, but they are not shown to users, and may be read but not added to or edited.
[bearbeiten] BOINC/Wiki authentication
A simple MediaWiki authentication plug-in allows users to be automatically authenticated to a wiki based on authentication to the BOINC project. All login/logout is taken care of by the BOINC page rather than the wiki.
[bearbeiten] Wiki linking in forums
Allow wiki-style links (eg. [[whatever]]) in the forums, with links to both our own co-locate wiki or to wikipedia (or others?)
[bearbeiten] Starboard screensaver application
Screensaver framework which allows one to use one of the many GL 'hacks' from XScreenSaver.
[bearbeiten] Future Features
These are ideas for features or modifications which we might like to try in the future, or work which may be in progress but not yet ready to test.
[bearbeiten] Error codes
In listing Results which have non-zero error code, extract the symbolic error code and possibly a longer explanation from the file error_numbers.h, the same file used to put the error codes in the client code.
[bearbeiten] Screensaver frame rate
Modify the throttled rendering loop to record the frame rate and fraction of CPU used by the graphics thread. Modify the way throttling is done based on the graphics fraction.
[bearbeiten] Preview before post
You must preview your message once before posting, and ideally you preview it several times until you explicitly press the „post“ button. We had this before, but then the underlying code changed so it needs to be done again.
[bearbeiten] RSS news source
Obtain RSS news from a file in html/cache if it exists, otherwise fall back to html/project as is current usage. (Do we check file modification times?) The array of news items is an associative array, rather than using numeric indices, but we keep the numeric indices (indeed add them if missing) for backward compatibility.
[bearbeiten] RSS news admin
the control panel page html/ops/news_admin.php presents the project administrator with a form which makes it very easy to add or edit RSS news.
[bearbeiten] Keyword classification
Postings can be classified by one (or someday more than one) keyword, which can then later be used to search for applicable postings. We had this before, but then the underlying code was changed in BOINC.
[bearbeiten] File attachments
Files of just about any type (image, log files, listings, text files) can be attached to a posting. Images are represented by a smaller icon version of the image.
[bearbeiten] New posting preview
In the list of discussion forums (forum_forum.php) show the title of the thread (or the leading part of the title if it's longer than some amount) of the thread with the newest post. We had this before, but then the underlying code was changed.
[bearbeiten] Role-based permissions
Permissions are granted to permission groups, and then users can be put into one or more of these groups. This makes granting permissions more flexible, as well as more easily extensible when we decide new permissions need to be added.
[bearbeiten] Room ownership and membership
Discussion rooms may be „owned“ by one or more users, who can control various settings, including how private the room is. A room could be restricted to only allow those users listed as „members“ to visit the room, or perhaps only members could post to the room. These more private rooms would not be listed in the main listing of discussion rooms.
[bearbeiten] Multiple affiliations
Users could be listed as members of more than one „team“. On I2U2 we use the „team“ to indicate the school the teacher or student is affiliated with. Some teachers may teach at more than one school, some students might take classes at or through more than one school (I did). This would be only for I2U2; it doesn't make much sense for BOINC. It might be best to just add a new DB field for this rather than pretending that the team mechanism works for school affiliation.
A member of the crew can give someone a link to the site with ?refered_by=#### with the refering crew member's userid. If the new person creates an account, and if that account later obtains X amount of credit, then the refering crew member gets a reward. The reward could be additional credits, or it could be project-specific (eg. dubloons).
[bearbeiten] Help Desk - recent questions
the Help Desk area only shows recent questions and replies (where recent is configurable - we've tried 3-7 days) so that it remains "fresh". But now this is turned on/off by the user via checkbox.