{"action":"created","issue":{"url":"https://api.github.com/repos/radical-cybertools/radical.ensemblemd/issues/62","labels_url":"https://api.github.com/repos/radical-cybertools/radical.ensemblemd/issues/62/labels{/name}","comments_url":"https://api.github.com/repos/radical-cybertools/radical.ensemblemd/issues/62/comments","events_url":"https://api.github.com/repos/radical-cybertools/radical.ensemblemd/issues/62/events","html_url":"https://github.com/radical-cybertools/radical.ensemblemd/issues/62","id":62745739,"number":62,"title":"Questions for the Profiling Utility","user":{"login":"iparask","id":8268665,"avatar_url":"https://avatars.githubusercontent.com/u/8268665?v=3","gravatar_id":"","url":"https://api.github.com/users/iparask","html_url":"https://github.com/iparask","followers_url":"https://api.github.com/users/iparask/followers","following_url":"https://api.github.com/users/iparask/following{/other_user}","gists_url":"https://api.github.com/users/iparask/gists{/gist_id}","starred_url":"https://api.github.com/users/iparask/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iparask/subscriptions","organizations_url":"https://api.github.com/users/iparask/orgs","repos_url":"https://api.github.com/users/iparask/repos","events_url":"https://api.github.com/users/iparask/events{/privacy}","received_events_url":"https://api.github.com/users/iparask/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/radical-cybertools/radical.ensemblemd/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-03-18T17:18:35Z","updated_at":"2015-03-20T15:59:45Z","closed_at":null,"body":"Trying to integrate the profiling utility some questions have risen, especially after the discussion I had with Mark.\r\nThe logentry of the CUs, I think, has changed significantly between what exists in the master and devel of RP. The message \"All FTW output staging directives done\" and the logentry attribute of the unit's logentry I think it does not exist in the devel of RP. If I am mistaken somewhere, please correct me.\r\n\r\nAssuming that the above observations are correct, I have a couple of questions.\r\n\r\n1) Should EnsembleMD know about the logentry of a CU, in the sense of using it to perform some work with it?\r\n2) Is it correct to use the messages that exist in the logentry as checks to get our timings? Should it be better if we used something more generic like CU states? I understand that the timestamp of each CU state exists in the logentry.\r\n"},"comment":{"url":"https://api.github.com/repos/radical-cybertools/radical.ensemblemd/issues/comments/84055623","html_url":"https://github.com/radical-cybertools/radical.ensemblemd/issues/62#issuecomment-84055623","issue_url":"https://api.github.com/repos/radical-cybertools/radical.ensemblemd/issues/62","id":84055623,"user":{"login":"iparask","id":8268665,"avatar_url":"https://avatars.githubusercontent.com/u/8268665?v=3","gravatar_id":"","url":"https://api.github.com/users/iparask","html_url":"https://github.com/iparask","followers_url":"https://api.github.com/users/iparask/followers","following_url":"https://api.github.com/users/iparask/following{/other_user}","gists_url":"https://api.github.com/users/iparask/gists{/gist_id}","starred_url":"https://api.github.com/users/iparask/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iparask/subscriptions","organizations_url":"https://api.github.com/users/iparask/orgs","repos_url":"https://api.github.com/users/iparask/repos","events_url":"https://api.github.com/users/iparask/events{/privacy}","received_events_url":"https://api.github.com/users/iparask/received_events","type":"User","site_admin":false},"created_at":"2015-03-20T15:59:45Z","updated_at":"2015-03-20T15:59:45Z","body":"I am referring to lines 43-48 of the script. Unfortunately, it can not run for my execution plugin and the reason is here [1]. I want to use the same code. There is no reason to have different profiling methodology between execution plugins. A quick around is to take the rest of the code and include it in my execution plugin and do the profiling from there, but I do not think it is a good idea since it over complicates things without any reason\r\n\r\n[1] https://github.com/radical-cybertools/radical.pilot/issues/501"}}