Bug #2489
closed
rawtransfer.py is not accurate with multiple dd camera and not efficient with multiple file servers
Added by Anchi Cheng about 11 years ago.
Updated about 11 years ago.
Assignee:
Sargis Dallakyan
Affected Version:
Appion/Leginon 3.0.0
Description
The temporary frame files or directory are time-stamped but not host specific. Although possibility is small, two camera may acquired the same time-stamped file name. In addition, if files need to be transferred onto more than one network drives, it would be more efficient to only transfer through the most efficient route. We have an example at TSRI where one group saves their data across the campus to large data condo storage while another uses a more local file server. The two are on different network switches.
r17846 adds options
--camera_host=CAMERA_HOST
Camera computer hostname in leginondb, e.g.
--camera_host=gatank2
--destination_head=PATH
Specific head destination frame path to transfer if
multiple frame transfer is run for one source to frame
paths not all mounted on the same computer, e.g.
--destination_head=/data1
Neither is required parameter
- Status changed from Assigned to In Code Review
- Assignee changed from Anchi Cheng to Jim Pulokas
Jim,
Please review this in case I am terribly wrong about what I set here.
- Status changed from In Code Review to In Test
- Assignee changed from Jim Pulokas to Anchi Cheng
Looks good. We also need to think about an init script so that we get back up after a reboot. And this init script needs to be able to run rawtransfer.py using these new arguments.
- Status changed from In Test to Closed
- Assignee changed from Anchi Cheng to Sargis Dallakyan
- Priority changed from High to Low
Sargis,
Just a reminder in case that you want to write an init script for this. The original bug is fixed.
Also available in: Atom
PDF