Notícias de última hora dos projectos BOINC

Obrigado pelo heads up, o meu tablet tem andado parado (nem o nativeboinc nem o boinc oficial correm direito no 4.2.2 e no 4.3 :(), mas em breve volto ao trabalho, desta vez no Seti :D
 
humm... telemóveis a BOINCAR... Pergunto se é saudável pro CPU estar a 100% tantas horas (e assumindo que isso só funciona quando tá a carregar)
 
humm... telemóveis a BOINCAR... Pergunto se é saudável pro CPU estar a 100% tantas horas (e assumindo que isso só funciona quando tá a carregar)

o meu GT-P1000 passou maio, junho e julho quase inteiros a boincar 24/7, ligado a corrente ou não, e muito desse tempo com overclock, e até agora 0 problemas. Mas pode variar de equipamento em equipamento, já li de pessoal que "estourou" a bateria (tenho lido stresses com HTC's...)
 
e o aquecimento? e mesmo sem ser ligado a corrente boincava? a bateria devia voar logo?

Nunca aqueceu muito (excepto no PrimeGrid, nunca corri o projecto durante mais de 5 minutos, vou experimentar de novo quando entrar o Inverno).

Eu tinha configurado para correr sempre, ligado ou não à corrente. A diferença é que quando ligava à corrente fazia um ligeiro underclock ao CPU para não stressar tanto a bateria.

Depende do projecto. No enigma, uma carga da-me para 6/7 horas de boinc. Para outros projectos dura menos, o minimo que me durou foi 4 horas. Depois podes programar para chegar aos X% de bateria e parar as tasks
 
No programa BOINC para Android pode-se especificar quando é que o programa usa o CPU. Pré-definido estão as seguintes definições:

- Mínimo de bateria: 90%
- Máximo de temperatura: 40º
- CPU cores: 1
- Pausar a 50% de utilização
- Máximo de espaço a utilizar: 90%
- Mínimo: 0.1GB
- Limite de RAM: 50%
 
No programa BOINC para Android pode-se especificar quando é que o programa usa o CPU. Pré-definido estão as seguintes definições:

- Mínimo de bateria: 90%
- Máximo de temperatura: 40º
- CPU cores: 1
- Pausar a 50% de utilização
- Máximo de espaço a utilizar: 90%
- Mínimo: 0.1GB
- Limite de RAM: 50%

Exactamente... Depois ha o NativeBoinc que já uso há muito tempo, que ainda tem mais opções. O novo cliente oficial que saiu há pouco é bonito, mas não é tão funcional, e a minha experiencia com ele diz-me que a app está constantemente a "desligar-se". O NativeBoinc não sofre de tantos problemas.
 
MilkyWay@Home a 26 de Setembro:

Users Auto-Aborting Work Units
Hello all,

It has come to our attention that some users have been setting their BOINC clients to auto abort work units from specific applications. Doing this sends an error results back to our server which then causes some work units to be unable to validate. Essentially, it prevents some of our hard working crunchers from getting their due credits. The proper way to prevent yourself from getting work units from a specific applications such as our beta applications N-Body or Modified Fit, is to go to your account page on our website (http://milkyway.cs.rpi.edu/milkyway/home.php). Under the Preferences section please select the link for your preferences for this project. There will then be a link to edit these preferences on this page. Halfway down your preferences, there will be some check boxes in the "Run only the selected applications" section. You will only receive work units for the applications you have check marks next to. For reference: Milkyway@home is our flagship application and is considered stable and in its final released state; Milkyway@home N-body Simulation is our beta version N-body simulation and orbit fit program; Milkyway@home Separation is an, as of now, unused application; Milkyway@home Separation (Modified Fit) is our beta version separation code testing new models for both streams and background in the Milky Way Halo. As usual if you have any issues with this method or questions about it please post them here. We appreciate your cooperation and understanding in this.

Thank you,

Jake W.

TL;DR: If you are auto-aborting work units please stop and use the method above to prevent users from losing credits and to prevent problems in our algorithms.
 
World Community Grid (via email):

Help researchers detect cancer earlier and design more effective treatments
We're excited to launch a new project on World Community Grid today - Mapping Cancer Markers.
Led by researchers from the Princess Margaret Cancer Center, Canada, Mapping Cancer Markers will scan data from thousands of patient tissue samples to identify chemical signatures ("markers") associated with particular types of cancer.
These results will help with earlier detection, better personalized treatments, and accelerate future research on cancer and other complex diseases.
Help power the search - if you're not already signed up, go to your My Projects page and add the Mapping Cancer Markers project today.
Thanks for all your support,
The World Community Grid Team
 
World Community Grid (via email):

Join us onDecember 6th for a live webcast with Dr. Stan Watowich, principal investigator for Discover Dengue Drugs - Together.
It's been over 4 years since the first phase of Discover Dengue Drugs - Together wrapped up on World Community Grid. Join this webcast for an update about the research team's progress, and an overview of how computational screening can help accelerate the search for treatments for many deadly diseases.
Hope you can join us!The webcast will begin at 1:00pm Eastern Time (USA) / 18:00 UTC. For more details and the link to the webcast, click here.
Thanks for all you do.
Sincerely,
The World Community Grid Team
 
Hello Boinc Family,


The Formula Boinc is modeled on Formula One World Championship, circuits are projects, times are team's points made on each project from 1 January to 31 December. Set your crunch to have the best production on many projects and you get points for the podium of best Boinc's contributors.
New rules for 2014: The teams will be sorted in leagues according to their RAC. See list here.


Link to the Formula-Boing website: http://formula-boinc.org/


Link detailing the divisions: http://formula-boinc.org/equipes.py?year=2014


Participation is automatic if your team runs more than 10 projects


Thank you for spreading the word within your team :)


Kind Regards


Ousermaatre on behalf of Steering committee FB.
 
World Community Grid (via email):

We're changing how we deliver research work to you.



We are going to change over to a new system for delivering research work to members on January 27th starting at 15:00 UTC. This change will provide better access to files that are frequently downloaded, and will offer better flexibility and expandability for future research projects. This will also allow World Community Grid to benefit from SoftLayer capabilities, an IBM cloud solutions provider.
For most volunteers, nothing will change - your devices will continue to receive tasks and process them as usual.
What you should know:

If you get a pop-up window on your device asking you to confirm that World Community Gird wants to connect to the internet, you should allow the connection.
If your firewall is manually configured, or you suspect your device is not receiving new research tasks, you may need to update your settings.

Thank you for your support,
The World Community Grid Team
 
PrimeGrid a 24 de Janeiro:

On 14 January 2014, 15:26:41 UTC, PrimeGrid’s 321 Prime Search project found the mega prime: 3*2^10829346+1 The prime is 3,259,959 digits long and enters Chris Caldwell's The Largest Known Primes Database ranked 12th overall. This is the largest known 321 mega prime and the largest prime found to date at PrimeGrid! The discovery was made by Sai Yik Tang (tomakey) of Malaysia using an Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz with 4 GB RAM running Microsoft Windows 7 Enterprise. This computer took about 17 hours and 40 minutes to complete the primality test using LLR. The prime was verified on 14 January 2014 20:23:24 UTC, by schnabelt of Germany using an Intel(R) Pentium(R) CPU G850 @ 2.90GHz with 4 GB RAM running Microsoft Windows 7 Enterprise. This computer took about 22 hours and 47 minutes to complete the primality test using LLR. For more details, please see the official announcement.


SETI@home a 29 de Janeiro:

SETI@home now supports Intel GPUs
We've released SETI@home 7.03 for Intel GPUs that support OpenCL 1.2. If you have an Intel GPU and want to use it to speed up SETI@home make sure that "Use Intel GPU" is set to "yes" in your Project Preferences.
 
Será que este openCL do GPU intel funciona mesmo com gráfica dedicada?

Se bem que me "retirei" do BOINC. Verão + pó + energia cara não dá...
 
Será que este openCL do GPU intel funciona mesmo com gráfica dedicada?

Já alguém testou? :)

World Community Grid (via email):

Hear Prof. Alessandra Carbone share how your computing time is helping her team understand muscular dystrophy.
Don't miss this opportunity to hear an in-depth explanation of the science behind the Help Cure Muscular Dystrophy project.
Muscular dystrophy is a complicated disorder that impairs muscle function. Finding better treatments begins with understanding the complex interactions between thousands of proteins potentially associated with the disease. World Community Grid members are making it possible for Professor Alessandra Carbone and her Help Cure Muscular Dystrophy research team to model and understand these protein-protein interactions.
Join us for the latest information about this exciting project. Check your browser compatibility, and then join the webcast February 6th at 11:00AM Eastern Time (USA) 16:00 UTC.

Thanks for all your support,

The World Community Grid Team
 
Back
Topo