Porting over Hermes Events to Chrome Format [Duplicate] about hermes-profile-transformer HOT 1 CLOSED

I went through how the Chrome Profiles do this and came across the Catapult Project which basically implements the trace-viewer for Chrome. I believe we can find the way to make sense of our code by digging deep through this repository

On some research I found this systrace/profile_chrome/main.py file to be relevant to what we want to achieve. My reasons for believing so are simply based on this line in the code. This leads us to this systrace/profile_chrome/profiler.py file where a CaptureProfile Method has been implemented, now the relevant line in this method is probably the tracing_controller, which leads us to the systrace/systrace/tracing_controller.py file containing tracing code, however such tracing code is also available at other locations, for example: ftrace_events, android_events. From what I understand, the tracing_controller mentioned earlier, aggregates the events generated by these events. For the purposes for this project, I think we should pay particular emphasis on the Android Agent. However, this does require an extremely deep dive into the code. I think we should confirm with @jevakallio if we are on the right path, or if I am mistaken here.

from hermes-profile-transformer.