{"id":264,"date":"2021-11-17T20:58:16","date_gmt":"2021-11-17T19:58:16","guid":{"rendered":"https:\/\/bslthemes.site\/luique\/?post_type=portfolio&p=264"},"modified":"2023-07-22T15:28:57","modified_gmt":"2023-07-22T13:28:57","slug":"chronos","status":"publish","type":"portfolio","link":"https:\/\/marcovogt.de\/index.php\/portfolio\/item\/chronos\/","title":{"rendered":"Chronos"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\n\t\t\n\t\t\t\t
\n\t\t\t\t\t\t

\n\t\t\t\t\n\t\t\t\t\tChronos\t\t\t\t<\/span>\n\t\t\t<\/h2>\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\n\t\t\t\t\tThe Swiss Army Knife for Systems Evaluations\t\t\t\t<\/span>\n\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The Chronos System is a comprehensive evaluation toolkit initially conceived for database systems evaluations but designed generically enough to be applicable in other domains. Its primary goal is to streamline and automate the system evaluation process, including setup, execution, and subsequent analysis, thereby saving significant amounts of time and eliminating manual tasks.<\/p>

Systems evaluations are an integral part of empirical research in computer science, involving the systematic assessment of systems based on various parameters. These evaluations often require systems to be run repeatedly with different parameter sets, which can be a time-consuming and repetitive task. The Chronos system revolutionizes this process by automating the entire evaluation workflow, requiring no human intervention once set up.<\/p>

The Chronos system offers several key features that make it an efficient and effective tool for system evaluations. It provides an easy-to-use interface for defining new experiments, scheduling their execution, monitoring progress, and analyzing results. The system can handle different systems simultaneously and is designed to support long-term evaluations by providing automated failure handling and recovery mechanisms. Results from evaluations, including parameter settings that led to those results, are stored and archived within the system for future reference. Moreover, Chronos facilitates the integration of existing evaluation clients and supports developers in creating new ones.<\/p>

The architecture of the Chronos system consists of two main components: Chronos Control and Chronos Agents. Chronos Control is the heart of the toolkit, providing a web UI and a RESTful API for managing evaluations. On the other hand, Chronos Agents interact with existing evaluation clients and leverage the REST API to obtain necessary information for evaluations. Chronos also has a built-in data model containing elements such as projects, experiments, evaluations, jobs, systems, and deployments, making it easier to manage and navigate the evaluation process.<\/p>

Since its inception, Chronos has been used for the evaluation of various research prototypes and has proven itself as an invaluable tool in academic and research settings. Its capacity for automation, coupled with its robust and adaptable features, positions Chronos as a vital tool for systematic systems evaluations across different domains. With the source code openly available on GitHub under the MIT open-source license, the Chronos system represents a significant contribution to empirical research in computer science<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t<\/i>\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\tGitHub<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t<\/i>\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\tWebsite<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t
<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"featured_media":2779,"menu_order":0,"template":"template-layout-builder.php","portfolio_categories":[],"class_list":["post-264","portfolio","type-portfolio","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/marcovogt.de\/index.php\/wp-json\/wp\/v2\/portfolio\/264","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/marcovogt.de\/index.php\/wp-json\/wp\/v2\/portfolio"}],"about":[{"href":"https:\/\/marcovogt.de\/index.php\/wp-json\/wp\/v2\/types\/portfolio"}],"version-history":[{"count":26,"href":"https:\/\/marcovogt.de\/index.php\/wp-json\/wp\/v2\/portfolio\/264\/revisions"}],"predecessor-version":[{"id":2780,"href":"https:\/\/marcovogt.de\/index.php\/wp-json\/wp\/v2\/portfolio\/264\/revisions\/2780"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/marcovogt.de\/index.php\/wp-json\/wp\/v2\/media\/2779"}],"wp:attachment":[{"href":"https:\/\/marcovogt.de\/index.php\/wp-json\/wp\/v2\/media?parent=264"}],"wp:term":[{"taxonomy":"portfolio_categories","embeddable":true,"href":"https:\/\/marcovogt.de\/index.php\/wp-json\/wp\/v2\/portfolio_categories?post=264"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}