Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[P2] Simulation traces are not understandable for human being #23

Open
tancheng opened this issue Nov 18, 2024 · 5 comments · May be fixed by #43
Open

[P2] Simulation traces are not understandable for human being #23

tancheng opened this issue Nov 18, 2024 · 5 comments · May be fixed by #43
Assignees
@yuqisun
Labels
documentation Improvements or additions to documentation new feature New feature or request test

Comments

@tancheng
Copy link
Owner 

5: [tile0]: 00000000.0.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0 => [(opt)1c|(in)1-2-3-4|(p)0|(out)5-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0] ([recv: 00000000.0.0.0,00000000.0.0.0,00000000.0.0.0,00000000.0.0.0] (ldcst)(P0) (const: 00000000.0.0.0, en: 1) ] = [out: 00000000.1.0.0,00000000.0.0.0] (recv_opt.rdy: 1, recv_in[0].rdy: 1, recv_in[1].rdy: 1, recv_predicate.msg: 0.0, (ldcst), recv_opt.en: 1, send[0].en: 1) ) => 00000000.1.1.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0 => 00000000.1.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0|00000000.0.0.0 => (00000000,1)|(00000000,0)|(00000000,0)|(00000000,0)(opt)1c|(in)1-2-3-4|(p)0|(out)5-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0 : [(opt)1c|(in)1-2-3-4|(p)0|(out)5-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0||(opt)1c|(in)1-2-3-4|(p)0|(out)5-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0||(opt)00|(in)0-0-0-0|(p)0|(out)0-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0||(opt)00|(in)0-0-0-0|(p)0|(out)0-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0||(opt)00|(in)0-0-0-0|(p)0|(out)0-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0||(opt)00|(in)0-0-0-0|(p)0|(out)0-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0||(opt)00|(in)0-0-0-0|(p)0|(out)0-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0||(opt)00|(in)0-0-0-0|(p)0|(out)0-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0] : (opt)1c|(in)1-2-3-4|(p)0|(out)5-0-0-0-0-0-0-0|(p_in)0-0-0-0-0-0||

I don't think existing simulation trace is human-friendly. HW-oriented development is not the way to go towards HW/SW co-design in my personal opinion. At least we need to add some prefix to each field to indicate what the waveform/data is for.
@tancheng tancheng added documentation Improvements or additions to documentation new feature New feature or request labels Nov 18, 2024
yuqisun added a commit to yuqisun/VectorCGRA that referenced this issue Dec 9, 2024
@yuqisun
Simulation traces are not understandable for human being tancheng#23
7f164e9
@yuqisun
Copy link
Collaborator

yuqisun commented Dec 16, 2024 •
edited
Loading

hi @tancheng , want to confirm the port order, is it same as

  1. xbarTypeList = ["W", "E", "N", "S", "NE", "NW", "SE", "SW"] or
  2. [NW(0, 0), N(0, 1) ... , SE(2, 2)] or
  3. {0: "NORTH", 1: "SOUTH", 2: "WEST", 3: "EAST", 4: "NORTHWEST", 5: "NORTHEAST", 6: "SOUTHEAST", 7: "SOUTHWEST"}

So I can add direction in the beginning of trace log:
north_inport: {'payload': Bits64(0x0000000000000000) ...
...

@tancheng
Copy link
Owner Author

I didn't get the second one, I thought that is just for GUI?
The first one can be found here? https://github.com/tancheng/CGRA-Flow/blob/29a942e4fdde2847f4bba5f1be1518e134bdfc84/mode_dark_light.py#L43, which is same as 3?

@yuqisun
Copy link
Collaborator

yuqisun commented Dec 16, 2024 •
edited
Loading

Ok, working to format in a markdown table, looks better?

Screenshot from 2024-12-15 19-39-34

@tancheng
Copy link
Owner Author

Looks awesome. I think this work is super ChatGPT-friendly...
Your markdown table inspires me that can we have sth similar to ↓?
image

@tancheng
Copy link
Owner Author

It could also be based on verbosity, i.e., verbosity == 1 shows above figure, verbosity == 2 shows your markdown; It could also be a GUI that can be clickable, i.e., click one tile in above figure, shows how the dataflow is happening on the selected cycle.

LOL, might be to much, you can make the call~! Markdown already looks fancy!

yuqisun added a commit to yuqisun/VectorCGRA that referenced this issue Dec 16, 2024
@yuqisun
Simulation traces are not understandable for human being tancheng#23
30d3a31
yuqisun added a commit to yuqisun/VectorCGRA that referenced this issue Dec 16, 2024
@yuqisun
Simulation traces are not understandable for human being tancheng#23
86de5ef
yuqisun added a commit to yuqisun/VectorCGRA that referenced this issue Dec 16, 2024
@yuqisun
Simulation traces are not understandable for human being tancheng#23
fe9ba2c
@tancheng tancheng mentioned this issue Dec 18, 2024
Open
yuqisun added a commit to yuqisun/VectorCGRA that referenced this issue Dec 19, 2024
@yuqisun
Simulation traces are not understandable for human being tancheng#23
73d5db8
yuqisun added a commit to yuqisun/VectorCGRA that referenced this issue Dec 19, 2024
@yuqisun
Simulation traces are not understandable for human being tancheng#23
899ebf9
yuqisun added a commit to yuqisun/VectorCGRA that referenced this issue Dec 19, 2024
@yuqisun
Simulation traces are not understandable for human being tancheng#23
2640d30
yuqisun added a commit to yuqisun/VectorCGRA that referenced this issue Dec 19, 2024
@yuqisun
Simulation traces are not understandable for human being tancheng#23
2f5f354
@tancheng tancheng linked a pull request Dec 25, 2024 that will close this issue
23 simulation traces are not understandable for human being #43
Open
@tancheng tancheng added the test label Jan 3, 2025
@tancheng tancheng changed the title Simulation traces are not understandable for human being [P2] Simulation traces are not understandable for human being Jan 3, 2025
@tancheng tancheng moved this to In Progress in CGRA Simulator Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yuqisun yuqisun

Labels
documentation Improvements or additions to documentation new feature New feature or request test
Projects
CGRA Simulator
Status: In Progress
Milestone
No milestone
2 participants
@tancheng @yuqisun