Marta Galimany
Marta Galimany (born 5 October 1985) is a Spanish long distance runner who specialises in the marathon.[1]
Personal information | |
---|---|
Full name | Marta Galimany Guasch |
Born | Valls, Spain | 5 October 1985
Sport | |
Sport | Track and field |
Event(s) | Marathon |
Achievements
Year | Competition | Venue | Position | Event | Notes |
---|---|---|---|---|---|
Representing | |||||
2016 | World Half Marathon Championships | Cardiff, United Kingdom | 53rd | Half marathon | 1:15:37 |
2018 | Mediterranean Games | Tarragona, Spain | 2nd | Half marathon | 1:15:16 |
European Championships | Berlin, Germany | 24th | Marathon | 2:38:25 | |
2019 | World Championships | Doha, Qatar | 16th | Marathon | 2:47:45 |
2018 World half marathon controversy
In 2018, both Carles Castillejo and Marta Galimany were selected by the Spanish National Athletics Federation to compete in the World Half Marathon Championships, among other five athletes per sex, being held in Valencia later that year. However, two days before the race, it was announced that a mistake took place by the federation while reading the rule book for that championships, and that the event only accepted 5 athletes per nation. Therefore, both Marta and Carles were ejected from the national team and could not compete in the event, what caused a massive controversy.[2]
Personal bests
Outdoor[3]
- 10,000 metres – 34:50.92 (Huelva 2017)
- 10 km – 33:08 (Valencia 2018)
- Half marathon – 1:11:13 (Seville 2020)
- Marathon – 2:29:02 (Seville 2020)
gollark: Denied.
gollark: ... no.
gollark: Thus bad.
gollark: It does NOT allow random access.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™️ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end, finds the latest versions and decompresses stuff at the right offsetThere are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
References
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.