{"push_id":845093279,"size":1,"distinct_size":1,"ref":"refs/heads/research/code-energy-footprint","head":"b91714ae313fcf096b108f111f7061615c5e0eac","before":"117d6d249cf4437ec39f3cb1b6e6b061d04d5241","commits":[{"sha":"b91714ae313fcf096b108f111f7061615c5e0eac","author":{"email":"8087404fbdd07c5fc5dabfc45455106612d1ab91@gmail.com","name":"Maxime Colmant"},"message":"feature(code-energy-footprint): allows to get the power consumption of a piece of code (represented as a label) from an external program\n\nThe method for configuring a PC is now more configurable and easier to use in different scenarios.\nDifferent picker is now available for creating or using file descriptors upon needs.\nCreates a UnixSocket server to handle the connexion with clients, to receive information and file descriptors from outside.\nCreates a new sensor for creating the server, for processing information sent by clients and for getting performance counter values from codes (represented as labels).\nUpdates the CLI for monitoring a piece of code (+ improvement).\n\nfeature(code-energy-analysis): adds an application for analyzing the traces of an instrumented program in order to obtain the power consumption of each call through the time.\n\nCreates an application to gather the power estimation of PowerAPI and the traces produced by an instrumented program.\nThe traces are processed to a global call graph, and the power consumption are then correlated to time spent per call.","distinct":true,"url":"https://api.github.com/repos/Spirals-Team/powerapi/commits/b91714ae313fcf096b108f111f7061615c5e0eac"}]}