Page 1 of 1

Last day of bigadv today ...

PostPosted: Sat Jan 31, 2015 10:46 am
by DocJonz
.. and its sad to say that communication on what happens next has been particularly poor from the Stanford end on this topic.
(There was a one-line comment from Vijay in Reddit that new projects were being set up for large core machines, but that's ALL the information the community has had).
So what is the plan for large core machines from tomorrow :?:

Re: Last day of bigadv today ...

PostPosted: Sat Jan 31, 2015 12:58 pm
by EXT64
So, I haven't been following it all that closely and forgot exactly how the announcement was worded: has this been confirmed as a hard cutoff, or is it like the "end" of Core 15 and Core 16 where no newer projects are made but some of the old still run their course (and afflict us with their terrible PPD :D ).

Re: Last day of bigadv today ...

PostPosted: Sat Jan 31, 2015 1:57 pm
by DocJonz
It was set in stone just over a year ago; "The BA experiment will permanently end on January 31, 2015. On that date, the servers will be set to accept only and we will have no plans for future BA WUs", see the full Vijay Blog.

Re: Last day of bigadv today ...

PostPosted: Sat Jan 31, 2015 3:25 pm
by ChristianVirtual

Re: Last day of bigadv today ...

PostPosted: Sat Jan 31, 2015 6:16 pm
by bruce
I'm locking this topic.

1) Vijay Pande's statements are authoritative and anything added by volunteers like myself would just be a guess.
2) This is now (and officially always has been) a community support forum and you're not requesting or providing support by volunteers.
3) If you have questions for the Pande Group, please visit the reddit linked in the OP.
4) This topic can stay as an additional announcement, in case anybody missed all of the other statements about the same subject.

Re: Last day of bigadv today ...

PostPosted: Sat Jan 31, 2015 8:08 pm
by kasson
Please note Prof. Pande's blog post as of today (linked above and below). The -bigadv flags will no longer be linked to the bigadv program (i.e. no separate points scheme) but will direct clients to work units that should scale well on large-core machines. The diversity of these work units is expected to expand in the future. At the moment, we don't have a roadmap we can share for this particular mechanism, but we will continue to do our best to ensure that large-core machines are matched with work units that they perform well on.

https://folding.stanford.edu/home/big-a ... anuary-31/