![\"enter](\"http://lgm.fri.uni-lj.si/wp-content/uploads/2018/07/TrackML-Vis.png\")
Dear contesters,
\n\nduring the past two months, we have been developing a visualization framework for visualizing the collision event data.
\n\nThe framework allows the user to browse/search through the events, tracks, and hits. One can select a track/hit and it will bring it in the focus. To make the tool even more useful, a user can upload his/her solution track and compare it with the ground truth data. The framework is built using ThreeJS and runs in web browser. To have access to the collision events of your choosing, you have to set the tool on your machine.
\n\nThe framework also allows users to change many visualization parameters such as colors and transparency of geometry and event data as well as making cut-off views of geometry data.
\n\nYou can find more information about the framework, the demo and the Git repository on the link below:\nhttp://lgm.fri.uni-lj.si/portfolio-view/high-energy-physics-event-visualisation-cern-collaboration/
\n\nIf you have any questions or comments regarding the tool please do contact me. We are always glad to get the feedback and to try and improve the solution.
\n\nYou can see a picture of the framework in action below.\n
Best regards,\nCiril Bohak
\n\nUniversity of Ljubljana\nFaculty of Computer and Information Science\nLaboratory for Computer Graphics and Multimedia
\n\nciril.bohak@fri.uni-lj.si, lgm.fri.uni-lj.si/ciril
", "messages": [ { "id": 361856, "postDate": "2018-07-25T07:49:38.707Z", "content": "Dear contesters,
\n\nduring the past two months, we have been developing a visualization framework for visualizing the collision event data.
\n\nThe framework allows the user to browse/search through the events, tracks, and hits. One can select a track/hit and it will bring it in the focus. To make the tool even more useful, a user can upload his/her solution track and compare it with the ground truth data. The framework is built using ThreeJS and runs in web browser. To have access to the collision events of your choosing, you have to set the tool on your machine.
\n\nThe framework also allows users to change many visualization parameters such as colors and transparency of geometry and event data as well as making cut-off views of geometry data.
\n\nYou can find more information about the framework, the demo and the Git repository on the link below:\nhttp://lgm.fri.uni-lj.si/portfolio-view/high-energy-physics-event-visualisation-cern-collaboration/
\n\nIf you have any questions or comments regarding the tool please do contact me. We are always glad to get the feedback and to try and improve the solution.
\n\nYou can see a picture of the framework in action below.\n
Best regards,\nCiril Bohak
\n\nUniversity of Ljubljana\nFaculty of Computer and Information Science\nLaboratory for Computer Graphics and Multimedia
\n\nciril.bohak@fri.uni-lj.si, lgm.fri.uni-lj.si/ciril
", "rawMarkdown": "Dear contesters,\n\nduring the past two months, we have been developing a visualization framework for visualizing the collision event data.\n\nThe framework allows the user to browse/search through the events, tracks, and hits. One can select a track/hit and it will bring it in the focus. To make the tool even more useful, a user can upload his/her solution track and compare it with the ground truth data. The framework is built using ThreeJS and runs in web browser. To have access to the collision events of your choosing, you have to set the tool on your machine.\n\nThe framework also allows users to change many visualization parameters such as colors and transparency of geometry and event data as well as making cut-off views of geometry data.\n\nYou can find more information about the framework, the demo and the Git repository on the link below:\n[http://lgm.fri.uni-lj.si/portfolio-view/high-energy-physics-event-visualisation-cern-collaboration/][1]\n\nIf you have any questions or comments regarding the tool please do contact me. We are always glad to get the feedback and to try and improve the solution.\n\nYou can see a picture of the framework in action below.\n![enter image description here][2]\n\n\n\nBest regards,\nCiril Bohak\n\nUniversity of Ljubljana\nFaculty of Computer and Information Science\nLaboratory for Computer Graphics and Multimedia\n\nciril.bohak@fri.uni-lj.si, lgm.fri.uni-lj.si/ciril\n\n [1]: http://lgm.fri.uni-lj.si/portfolio-view/high-energy-physics-event-visualisation-cern-collaboration/\n [2]: http://lgm.fri.uni-lj.si/wp-content/uploads/2018/07/TrackML-Vis.png", "votes": 23 }, { "id": 362572, "postDate": "2018-07-26T16:16:31.547Z", "content": "Awesome!\nI really like how you managed to visualize the complex detector layouts so clearly. It made it much easier for me to see how the detectors were built up, and how particles can move between them.
\n\nI'm looking forward to using it for debugging and investigation of particular tracks and hits. Just now, I tried to investigate a single track by ID (598982942345142274), but it doesn't seem like the searchTrackID function can find it.\nI did as slight bit of investigation, and it looks like a problem stemming from (at some point) representing the trackID by a floating point number (default number representation in javascript), which makes rounding errors for some trackIDs. This is f.ex. indicated by the fact that 175642928088088576 is present in event000001000-particles.csv, while 175642928088088580 is the closest ID in the searchTrackID.
\n\nFor now a workaround is to search for the first part (say up until last 3 digits) of the trackID, and then pick the closest match manually from the list.
\n\nWould be cool if you could look into the problem. Anyway, thanks for sharing!
", "rawMarkdown": "Awesome!\nI really like how you managed to visualize the complex detector layouts so clearly. It made it much easier for me to see how the detectors were built up, and how particles can move between them.\n\nI'm looking forward to using it for debugging and investigation of particular tracks and hits. Just now, I tried to investigate a single track by ID (598982942345142274), but it doesn't seem like the searchTrackID function can find it.\nI did as slight bit of investigation, and it looks like a problem stemming from (at some point) representing the trackID by a floating point number (default number representation in javascript), which makes rounding errors for some trackIDs. This is f.ex. indicated by the fact that 175642928088088576 is present in event000001000-particles.csv, while 175642928088088580 is the closest ID in the searchTrackID.\n\nFor now a workaround is to search for the first part (say up until last 3 digits) of the trackID, and then pick the closest match manually from the list.\n\nWould be cool if you could look into the problem. Anyway, thanks for sharing!", "votes": 1, "replies": [ { "id": 362700, "postDate": "2018-07-27T00:06:20.510Z", "content": "Thank you for your comment. The issue has been fixed. Now you should be able to use full ID strings within search input.
", "rawMarkdown": "Thank you for your comment. The issue has been fixed. Now you should be able to use full ID strings within search input.", "votes": 2 } ] }, { "id": 367147, "postDate": "2018-08-07T07:20:48.490Z", "content": "@Ciril just now visited the link. awesome work ... great visualizations ..
", "rawMarkdown": "@Ciril just now visited the link. awesome work ... great visualizations .. ", "replies": [ { "id": 367176, "postDate": "2018-08-07T08:50:00.670Z", "content": "Thank you. We're glad you like it and hopefully find it useful as well.
", "rawMarkdown": "Thank you. We're glad you like it and hopefully find it useful as well." } ] }, { "id": 366591, "postDate": "2018-08-05T23:20:02.493Z", "content": "@ciril, thanks for this great tool.\nOne question, do you have the exact location of every channel inside the cells?
", "rawMarkdown": "@ciril, thanks for this great tool.\nOne question, do you have the exact location of every channel inside the cells?\n", "replies": [ { "id": 366655, "postDate": "2018-08-06T07:03:12.950Z", "content": "Hi @cosmojo,
\n\nwe have the same data as is available to competitors of the challenge, I do not think we have the exact location of every channel inside the cell though.
", "rawMarkdown": "Hi @cosmojo,\n\nwe have the same data as is available to competitors of the challenge, I do not think we have the exact location of every channel inside the cell though.\n" } ] }, { "id": 361898, "postDate": "2018-07-25T09:19:58.810Z", "content": "Thanks. Cool stuff.
", "rawMarkdown": "Thanks. Cool stuff.", "replies": [ { "id": 362598, "postDate": "2018-07-26T17:25:45.787Z", "content": "Thank you.
", "rawMarkdown": "Thank you." } ] }, { "id": 362844, "postDate": "2018-07-27T08:41:39.730Z", "rawMarkdown": "", "isDeleted": true, "replies": [ { "id": 362903, "postDate": "2018-07-27T11:12:50.847Z", "content": "Thank you. We try our best.
", "rawMarkdown": "Thank you. We try our best." } ] } ], "comments": [ { "id": 362572, "author_name": "icecuber", "author_url": "", "post_date": "2018-07-26T16:16:31.547000", "content": "Awesome!\nI really like how you managed to visualize the complex detector layouts so clearly. It made it much easier for me to see how the detectors were built up, and how particles can move between them.
\n\nI'm looking forward to using it for debugging and investigation of particular tracks and hits. Just now, I tried to investigate a single track by ID (598982942345142274), but it doesn't seem like the searchTrackID function can find it.\nI did as slight bit of investigation, and it looks like a problem stemming from (at some point) representing the trackID by a floating point number (default number representation in javascript), which makes rounding errors for some trackIDs. This is f.ex. indicated by the fact that 175642928088088576 is present in event000001000-particles.csv, while 175642928088088580 is the closest ID in the searchTrackID.
\n\nFor now a workaround is to search for the first part (say up until last 3 digits) of the trackID, and then pick the closest match manually from the list.
\n\nWould be cool if you could look into the problem. Anyway, thanks for sharing!
", "votes": 1, "replies": [ { "id": 362700, "author_name": "ss4774", "author_url": "", "post_date": "2018-07-27T00:06:20.510000", "content": "Thank you for your comment. The issue has been fixed. Now you should be able to use full ID strings within search input.
", "votes": 2, "replies": [] } ] }, { "id": 367147, "author_name": "Kishore M", "author_url": "", "post_date": "2018-08-07T07:20:48.490000", "content": "@Ciril just now visited the link. awesome work ... great visualizations ..
", "votes": 0, "replies": [ { "id": 367176, "author_name": "Ciril", "author_url": "", "post_date": "2018-08-07T08:50:00.670000", "content": "Thank you. We're glad you like it and hopefully find it useful as well.
", "votes": 0, "replies": [] } ] }, { "id": 366591, "author_name": "cosmojo", "author_url": "", "post_date": "2018-08-05T23:20:02.493000", "content": "@ciril, thanks for this great tool.\nOne question, do you have the exact location of every channel inside the cells?
", "votes": 0, "replies": [ { "id": 366655, "author_name": "Ciril", "author_url": "", "post_date": "2018-08-06T07:03:12.950000", "content": "Hi @cosmojo,
\n\nwe have the same data as is available to competitors of the challenge, I do not think we have the exact location of every channel inside the cell though.
", "votes": 0, "replies": [] } ] }, { "id": 361898, "author_name": "YaGana Sheriff-Hussaini", "author_url": "", "post_date": "2018-07-25T09:19:58.810000", "content": "Thanks. Cool stuff.
", "votes": 0, "replies": [ { "id": 362598, "author_name": "Ciril", "author_url": "", "post_date": "2018-07-26T17:25:45.787000", "content": "Thank you.
", "votes": 0, "replies": [] } ] }, { "id": 362844, "author_name": "", "author_url": "", "post_date": "2018-07-27T08:41:39.730000", "content": "", "votes": 0, "replies": [ { "id": 362903, "author_name": "Ciril", "author_url": "", "post_date": "2018-07-27T11:12:50.847000", "content": "Thank you. We try our best.
", "votes": 0, "replies": [] } ] } ], "raw_markdown_by_id": { "361856": "Dear contesters,\n\nduring the past two months, we have been developing a visualization framework for visualizing the collision event data.\n\nThe framework allows the user to browse/search through the events, tracks, and hits. One can select a track/hit and it will bring it in the focus. To make the tool even more useful, a user can upload his/her solution track and compare it with the ground truth data. The framework is built using ThreeJS and runs in web browser. To have access to the collision events of your choosing, you have to set the tool on your machine.\n\nThe framework also allows users to change many visualization parameters such as colors and transparency of geometry and event data as well as making cut-off views of geometry data.\n\nYou can find more information about the framework, the demo and the Git repository on the link below:\n[http://lgm.fri.uni-lj.si/portfolio-view/high-energy-physics-event-visualisation-cern-collaboration/][1]\n\nIf you have any questions or comments regarding the tool please do contact me. We are always glad to get the feedback and to try and improve the solution.\n\nYou can see a picture of the framework in action below.\n![enter image description here][2]\n\n\n\nBest regards,\nCiril Bohak\n\nUniversity of Ljubljana\nFaculty of Computer and Information Science\nLaboratory for Computer Graphics and Multimedia\n\nciril.bohak@fri.uni-lj.si, lgm.fri.uni-lj.si/ciril\n\n [1]: http://lgm.fri.uni-lj.si/portfolio-view/high-energy-physics-event-visualisation-cern-collaboration/\n [2]: http://lgm.fri.uni-lj.si/wp-content/uploads/2018/07/TrackML-Vis.png", "362572": "Awesome!\nI really like how you managed to visualize the complex detector layouts so clearly. It made it much easier for me to see how the detectors were built up, and how particles can move between them.\n\nI'm looking forward to using it for debugging and investigation of particular tracks and hits. Just now, I tried to investigate a single track by ID (598982942345142274), but it doesn't seem like the searchTrackID function can find it.\nI did as slight bit of investigation, and it looks like a problem stemming from (at some point) representing the trackID by a floating point number (default number representation in javascript), which makes rounding errors for some trackIDs. This is f.ex. indicated by the fact that 175642928088088576 is present in event000001000-particles.csv, while 175642928088088580 is the closest ID in the searchTrackID.\n\nFor now a workaround is to search for the first part (say up until last 3 digits) of the trackID, and then pick the closest match manually from the list.\n\nWould be cool if you could look into the problem. Anyway, thanks for sharing!", "367147": "@Ciril just now visited the link. awesome work ... great visualizations .. ", "366591": "@ciril, thanks for this great tool.\nOne question, do you have the exact location of every channel inside the cells?\n", "361898": "Thanks. Cool stuff.", "362844": "" } }