For sake of completeness, I wrote the following back in Spetember:
While sorting by task name is useful at times, if you're trying to find a particular task, in general you'd want to see the tasks in order of task id - which amount to ordering by send time/date. Would it be possible to get custom column sorting instead (e.g. by clicking on the column head)? That would also make it possible to sort by device, i.e. find CPU/GPU tasks quickly, something that is sadly missing atm. The search function is useful, but would profit from allowing wildcards. 2014-02-14 11:39 GMT+01:00 Richard Haselgrove <[email protected]> : > Having had a few months' experience with this, I wonder if we could > fine-tune it, especially for SETI Beta. > > The search box is wonderful, and ideal for the purpose. > > But unconditionally sorting tasks by name when names are displayed can > actually be a hindrance. > > SETI Beta deliberately keeps tasks in the database, unpurged, for months > or sometimes years. At the same time, like any active Beta project, most > attention is focused on recently-modified application versions. > > This morning, I was trying to assess whether a particular failure mode > might be associated with a particular task type (those with ".vlar" in the > name) - and I found I couldn't combine "show name" with "recent". > > The ideal solution would be to have sort links in the column headers, > independent of display format - as, I believe, was suggested to you > privately at the time. > > > > >________________________________ > > From: David Anderson <[email protected]> > >To: Richard Haselgrove <[email protected]> > >Cc: BOINC Developers Mailing List <[email protected]> > >Sent: Monday, 9 September 2013, 3:22 > >Subject: Re: [boinc_dev] new GUI RPC for getting completed /reported tasks > > > > > >Good idea! I made the following changes to the web code: > > > >- if you click "show name" in the task list, tasks are sorted > > by name instead of ID > > > >- you can search for tasks by name. > > > >This is deployed on SETI@home and SETI@home beta. > > > >-- David > > > >On 08-Sep-2013 1:22 PM, Richard Haselgrove wrote: > >> This looks very useful, both for application developers/testers, and > when > >> helping volunteers diagnose faults via a project message board. > >> > >> But either process is slowed down and made harder by a missing link in > the chain. > >> > >> The local client knows a task only by its name, as in the list below. > >> The project website default display (except at Einstein) displays Task > IDs for > >> results - and always displays tasks in order of ID #, even when > displaying names. > >> > >> It would be most helpful to be able to associate names and Task IDs - > either by > >> passing the Task ID # to the client in the <result> block when > allocating the > >> task, or by adding a task name search facility to the task listing > pages on > >> project websites. > >> > >> > > -------------------------------------------------------------------------------- > >> *From:* David Anderson <[email protected]> > >> *To:* BOINC Developers Mailing List <[email protected]> > >> *Sent:* Sunday, 8 September 2013, 20:54 > >> *Subject:* [boinc_dev] new GUI RPC for getting completed /reported > tasks > >> > >> Fred (developer of BoincTasks) pointed out that it's hard for GUIs > >> to learn the outcome of completed tasks, > >> since the interval from when the task completes to when it's > reported > >> can be just a few seconds, > >> and after this the client forgets about the task. > >> > >> To address this problem, I did the following: > >> > >> - the client keeps an in-memory list of tasks that have been > reported > >> in the last hour. > >> For each tasks it stores > >> - the project URL > >> - the result name > >> - the app name > >> - the final elapsed time > >> - the exit status > >> - the time when the task completed > >> - the time when the task was reported > >> > >> - There's a new GUI RPC, get_old_tasks(), which fetches this list. > >> > >> This feature will be in the next client release. > >> > >> -- David > >> _______________________________________________ > >> boinc_dev mailing list > >> [email protected] <mailto:[email protected]> > >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > >> To unsubscribe, visit the above URL and > >> (near bottom of page) enter your email address. > >> > >> > > > > > > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
