William H. Hilarides

William Hilarides is a Vice Admiral in the United States Navy.

Early life and education

Raised in Chicago, he graduated from the U.S. Naval Academy in 1981 with a Bachelor of Science in Physics. After graduation, he served as master of the Naval Academy Sailing Squadron sloop Avenger, competing in numerous offshore racing events.[1]

He holds a master's degree in engineering management from the Catholic University of America, completed the Air Force Command and Staff College, the Massachusetts Institute of Technology Seminar XXI Program in International Security Affairs and numerous acquisition schools.[1]

Prior to command, he served at sea aboard USS Pargo, USS Gurnard and USS Maryland, deploying to the North Atlantic, Mediterranean, Arctic and Western Pacific, as well as conducting several strategic deterrent patrols. Ashore, he served on the staff of Commander Submarine Force, U.S. Atlantic Fleet; Bureau of Naval Personnel; Joint Staff; and the staff of the chief of naval operations.[1]

Hilarides commanded USS Key West from May 1998 to November 2000 in Pearl Harbor. In command, he deployed to the Western Pacific and conducted a major shipyard maintenance period.[1]

Since becoming an acquisition professional in 2002, he has served as director, Advanced Submarine Research and Development, program manager of the SSGN Program and program executive officer for submarines, where he was responsible for all new construction submarine programs, along with the acquisition and life cycle maintenance of submarine weapons, countermeasures, sonar, combat control and imaging systems.[1]

Hilarides became the 43rd commander of Naval Sea Systems Command (NAVSEA) June 7, 2013. As NAVSEA commander, he overseaw a global workforce of more than 56,000 military and civilian personnel responsible for the development, delivery and maintenance of the Navy’s ships, submarines and systems.[1] Hilarides retired on 10 June 2016.[2]

Awards

Hilarides has received various personal and campaign awards, including the Distinguished Service Medal, the Defense Superior Service Medal, the Legion of Merit and the Meritorious Unit Commendation.[1]

gollark: The stages of git clone are: Receive a "pack" file of all the objects in the repo database Create an index file for the received pack Check out the head revision (for a non-bare repo, obviously)"Resolving deltas" is the message shown for the second stage, indexing the pack file ("git index-pack").Pack files do not have the actual object IDs in them, only the object content. So to determine what the object IDs are, git has to do a decompress+SHA1 of each object in the pack to produce the object ID, which is then written into the index file.An object in a pack file may be stored as a delta i.e. a sequence of changes to make to some other object. In this case, git needs to retrieve the base object, apply the commands and SHA1 the result. The base object itself might have to be derived by applying a sequence of delta commands. (Even though in the case of a clone, the base object will have been encountered already, there is a limit to how many manufactured objects are cached in memory).In summary, the "resolving deltas" stage involves decompressing and checksumming the entire repo database, which not surprisingly takes quite a long time. Presumably decompressing and calculating SHA1s actually takes more time than applying the delta commands.In the case of a subsequent fetch, the received pack file may contain references (as delta object bases) to other objects that the receiving git is expected to already have. In this case, the receiving git actually rewrites the received pack file to include any such referenced objects, so that any stored pack file is self-sufficient. This might be where the message "resolving deltas" originated.
gollark: UPDATE: this is wrong.
gollark: > Git uses delta encoding to store some of the objects in packfiles. However, you don't want to have to play back every single change ever on a given file in order to get the current version, so Git also has occasional snapshots of the file contents stored as well. "Resolving deltas" is the step that deals with making sure all of that stays consistent.
gollark: A lot?
gollark: probably.

References
  1. "William Hilarides". United States Navy Biography. United States Navy. Retrieved 4 February 2017. This article incorporates text from this source, which is in the public domain.
  2. Eckstein, Megan (10 June 2016). "Vice Adm. Moore Takes Command of Naval Sea Systems Command; Hilarides Retires". United States Naval Institute. Retrieved 3 February 2017.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.