Hello
Please can you tell me how to get the BOINC Transfers tab to show the completed, historical transfers.
When i click on this tab it is always empty - presumably because it is only showing current transfers
I would appreciate your help
Thanks
Emma

Completed transfers of any kind show in the event log (CTRL+SHIFT+E) and as long as you left the file_xfer flag intact in cc_config.xml.
For more verbosity, it's possible to add file_xfer_debug

---

great thank you
I can view the uploads in the Event Log which is good
It is a shame the transfers tab is always empty - it would be good if it could show completed transfers to make it easy to check everything is working

Or you can think, if there's nothing in the Transfers tab, everything is OK. :)
If there are things waiting in the Transfers tab, it is because you paused Network activity, or because the project is down.

You need a 3rd party application like Efmer's BOINCTASKS running along with BOINC to view/store your transfer history.

BoincTasks the visual BOINC interface, the ideal way to view your BOINC tasks.
BoincTasks can be used to manage a single computer locally or all your computers remotely.
Handles even larger amounts of Tasks/Wu well, and makes it ideal for computers with GPU.
Supports an unlimited number of remote computers.

... show the completed, historical transfers.

As Ageless has mentioned, the transfers tab shows things waiting to transfer so will only continue to show anything if there is a problem.

Please understand that the return of completed work is usually a 2-stage process, data gets transferred (eg. to an upload server at the project) and after that has completed, the task gets 'reported'. The 'reporting' is usually done automatically by the client and its purpose is to tell the project that your particular processed data is now sitting on the upload server waiting to be checked and (if valid) entered into the online database of completed results. So if you really want to check that all is OK with your returned work, you can go to the project website and look at your tasks list in the online database to see if there were any problems with what was sent back.

You also have a 'history record' of all returned results, a bit like the event log, on your computer. The event log is convenient to use because you can pull it up into a window to look at it using BOINC Manager. The event log is actually stored as a text file called stdoutdae.txt in your BOINC Data directory. Your results history is not quite as convenient since there is no nice clickable link to it in BOINC Manager. The history file (also in your BOINC Data directory) is called job_log_<project_dir_name>.txt where the 'name' part is the name of the project directory where all the files for a particular project are stored on your computer. You will have one of these 'job_logs' for each different project that you support. I run Einstein so my job logs are called 'job_log_einstein.phys.uwm.edu.txt'.

Each record in these text files gives details about a particular task your computer has returned. It's like a big spreadsheet. It's pretty easy to import the file into a spreadsheet if you want to analyse all the tasks your computer has returned. The important fields for each record are things like, Date/time when task was returned, Estimated crunch time when the task arrived, FLOPS estimate of the work content of the task, CPU time that the task actually took, Total (elapsed) time the task actually took, Task name.

I know it's a bit of work, but if you're interested in stats about your particular computer's performance and you have basic spreadsheet skills, you can import the job log file and do all sorts of things with it.

---

Cheers,
Gary.

Thank you all for your very helpful replies, I appreciate it and have learned a lot
Thank you
Emma