Auto saved by Logseq

2025-06-02 17:15:13 +02:00
commit d9ea3d552d
6279 changed files with 711145 additions and 0 deletions
@@ -0,0 +1,15 @@
+type:: [[REVIEWS]]
+full-title:: A Visual Notation for Succinct Program Traces
+title:: COLA-D-22-00029_reviewer
+date:: [[07-12-2022]] - 19:08
+status:: [[DONE]]
+venue:: [[COLA]]
+year:: 2022
+external-links:: [Editorial Manager®](https://www.editorialmanager.com/cola/default2.aspx)
+file:: ![COLA-D-22-00029_R1_reviewer.pdf](../assets/COLA-D-22-00029_R1_reviewer_1670436819946_0.pdf)
+
+	- I thank the reviewer for the refined version of the paper, especially for the added information about the implemented web-based GUI of the proposed approach. In my opinion, the following actions need to be done before the acceptance of the paper:
+		- I thank the authors again for the tool available at http://tracr.engr.oregonstate.edu/; however, further than referring to the whole document available at https://ir.library.oregonstate.edu/concern/graduate_projects/9306t607n I suggest to write a short HOWTO to explain potentially interested readers to play with the tool on an illustrative example.
+		- I would smooth all the statements like "user can **effectively** and **quickly** transform traces..." because they have not been evaluated. I can understand that doing a user study can be a lot of work; thus, I recommend smoothing statements that have not been evaluated.
+	- As a very minor remark, when doing journal revisions, I recommend marking in different colours paper additions or changes, so that the reviewer does not have to do manual diffs to focus on the changed parts of the revised paper.
+	- [[Highlights]]