Gilthanis
[H]ard|DCer of the Year - 2014
- Joined
- Jan 29, 2006
- Messages
- 8,735
LHC T4T has a new link. http://lhcathome2.cern.ch/vLHCathome/ and they are expanding for new apps.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Have they said what version of GROMACS they are using? I know some of the newer versions have some nice speedups and AVX (not sure of the gains). Scaling, as we know from F@h, will depend on the size of the simulation.
New x86 SIMD non-bonded kernels for the usual cut-off scheme, called group scheme and the new verlet scheme, use x86 SIMD intrinsics (no more assembly code):
SSE2
SSE4.1
AVX-128-FMA (for AMD Bulldozer/Piledriver)
AVX-256 (for Intel Sandy/Ivy Bridge)
Summary
In response to President Obama's call to action on the Climate Data Initiative, we invite scientists studying climate change issues to submit proposals for accessing massive supercomputing power to advance their research.....
This application uses SSE2 instruction sets. This makes the application 20 times faster. We did a scan and it appears that we had 40 computers that were active in that week that did not have Pentium 4 or above with SSE2 instructions. Basically to allow the application to run on these older processors, it would do WAY more harm to the speed of the overall project by not running SSE2. This application will not run on processors without SSE2 instructions.
Thanks,
-Uplinger
The initial memory requirements are going to be rather low. I would say less than 50MB. The bandwidth usage for this project may be large for runtime of a work unit. The work units we tested in this beta were small.
Remember this is just initial data and can change when we get closer to release.
Thanks,
-Uplinger
project unification
Hi Everyone,
So I want to try and start unifying the projects to simplify server updates, checking the forums, etc. Before I get going I want a little feedback as to what I'm planning so everyone is okay with it.
Basically, I'm going to create a new project (probably called "Citizen Science Grid") or something along those lines. Unfortunately, because people have different accounts on each project I can't do an automatic merge of the users and databases. So this means you'd have to create a new account on the new project (when the new project starts those will be the only forums for the site).
When the new project is up and going, I'll allow everyone to transfer their credit from their other accounts via a webpage (basically if you're logged in, you can enter in the user name and id of your account on citizen science grid, hit okay and it will transfer the credit over). So a couple questions about this approach:
1. will it break the credit trackers too badly? I'll subtract credit on the old project to 0, and then add the same amount of credit to the new account on citizen science grid.
2. I kind of want to keep credit for the different projects separate; if I keep different tables and export the stats of each project as it's own part of XML, will that cause any problems? Or would everyone rather just have one combined credit for each of the projects here (Wildlife@Home, DNA@Home, and SubsetSum@Home -- we'll probably be launching another one in the fall as well, so I want to get this done before we go doing that).
So, once I get some feedback, and if people don't have too many issues with this I'll set up the new project and get things started. Otherwise back to the drawing board.
thanks, hope to hear from you soon about this!
--Travis 1 Aug 2014, 0:27:01 UTC · Comment
Hi Everyone,
I've come up with what will hopefully be a good solution to the project unification. I've created a new project called Citizen Science Grid, which you can take a look at here (note it's very rough and i'm still working on a lot of the webpages to unify everything):
http://volunteer.cs.und.edu/csg/alpha/index.php
Since Wildlife@Home has been the most recently active project, I'm re-using the Wildlife@Home database for this project. Note that this project won't export statistics. Instead, credit earned by this project will be exported into the various sub projects.
So this means if you run Wildlife@Home only, you don't need to do anything. If you run any of the other projects, first make an account on Wildlife@Home (or on the Citizen Science Grid webpage) if you don't have one already.
I'm currently working on a webpage where you'll be able to link the account on Citizen Science Grid/Wildlife@Home to your accounts on DNA@Home or SubsetSum@Home. You'll need to enter in your user name and email for the account you want to link it to. Then when you generate credit it will be generated for that old account.
In a week or so I'm going to shut down the forums on SubsetSum@Home and DNA@Home, because they're going to just use the forum on Citizen Science Grid. That way all projects will be using the same forum.
Does that sound okay?
--Travis
I started running projects because I saw a huge wasted potential for idle systems. It later grew to the love of the science. Then morphed into competitiveness. And then has evolved into social structure with potential of real results.
But that is just me. However, I do agree that there is no happy fix. We just get used to it and keep on trucking. My biggest suggestion is just compare what you want to compare and ignore the rest.
Gilthanis [H]ard|DCer of the Month - July 2013/July 2014, 8.6 Years
I started running projects because I saw a huge wasted potential for idle systems. It later grew to the love of the science. Then morphed into competitiveness. And then has evolved into social structure with potential of real results.
But that is just me. However, I do agree that there is no happy fix. We just get used to it and keep on trucking. My biggest suggestion is just compare what you want to compare and ignore the rest.
__________________
You contradicted your own statement, you are running BitcoinUtopia why ? Answer = Because of the points
+1That is ridiculous.
http://stats.free-dc.org/stats.php?page=projmain
Preliminary Change Log 7.4.19 -> 7.4.20
MGR: Fix bug which sometimes made project description text in Simple View too wide to read.
MGR: Fix bug in initial layout of Simple View project panel.
MGR: Ensure that the advanced computing preferences dialog is wide enough to fit all its tabs.
MGR: Set background color according to skin in Simple View dialogs; this is a slight cosmetic tweak for checkboxes on Windows 7, which have a narrow border using the background color at their bottom and right side; also don't use magenta background color for debugging backgrounds unless specifically requested by setting a new define TEST_BACKGROUND_WITH_MAGENTA_FILL to non-zero.
MGR: Cosmetic fix: eliminate brief display of all tasks when switching from Simple View to Advanced View when Show only active tasks is selected.
client: if a project's app_config.xml has no errors, remove old notices.
client: display XML in app_config notices correctly.
compile fix for FreeBSD; from Steffen.
MGR: Remove non-ASCII Ellipse. I'm not sure the code chunk is even used anymore.
LOCALE: Update BOINC Manager template.
LOCALE: Line feed fixes?
locale: Update compiled localization files.
MGR: Fix localization of menu item labels in BOINC Manager menu on Mac for wxWidgets 3.0; restore use of mac-specific UTF-8 ellipsis character so as not to invalidate old localizations of "Preferences..." menu item.
Mac Installer & MGR: delete BOINC Manager's wxSingleInstanceChecker lock file in case wxSingleInstanceChecker failed to delete it (such as due to a crash.)
Preliminary Change Log 7.4.20 -> 7.4.21
Quick Version Fix
Build break fix for Windows.