Skip to content

Feature/estimate data transfer times#4

Open
mesham wants to merge 38 commits into
mainfrom
feature/estimate_data_transfer_times
Open

Feature/estimate data transfer times#4
mesham wants to merge 38 commits into
mainfrom
feature/estimate_data_transfer_times

Conversation

@mesham

@mesham mesham commented Oct 27, 2021

Copy link
Copy Markdown
Contributor

No description provided.

Max Kontak and others added 30 commits August 12, 2020 15:33
Based on the mean of old transfers between the source and destination machine the time for
the new transfer is computed
db-query returns the 10 last entries of data transfers between the machines (sorted by date_started)
time estimation checks if any entry is returned. TODO: what if no entries are returned?
the database query for estimating the transfertime searches for machines with name source and destination
Added console output, if no matching entries are found.
System health screen showed some errors in code, which are corrected now
We meassure the transferrate in bytes per seconds. We get the time of the transfer via the timedelta object.
Changed script to srun script.
Added a template directory.
Knapp and others added 8 commits April 1, 2021 11:30
Testing the current version on the cluster showed some bugs, which are fixed now.
If the optional entry transfer_rate is not set, search for None
Corrected the paths, such that they point into my directories
Changed the machine from ARCHER to HPDA
Added comments to the new functions
Added new data-field estimated_time to a DataTransfer entry to store the estimated time.
Added new entry estimated_time in the DataTransfer-package
Added new entry Estimation in the VESTEC-GUI
downloads the newest weather data from nasa to the system
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants