Mobiusi commited on
Commit
8208cf6
·
verified ·
1 Parent(s): 1007e26

update dataset card

Browse files
Files changed (1) hide show
  1. README.md +38 -0
README.md ADDED
@@ -0,0 +1,38 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: cc-by-nc-sa-4.0
3
+ task_categories:
4
+ - text-classification
5
+ language:
6
+ - en
7
+ pretty_name: Co-Simulation Scheduling and Time Synchronization Code Understanding Dataset
8
+ ---
9
+
10
+ # Co-Simulation Scheduling and Time Synchronization Code Understanding Dataset
11
+
12
+ This dataset contains source code understanding samples focused on co-simulation master controllers and scheduling components, including simulation step sizes, execution order, time advancement, and synchronization control. Each sample pairs source code with an analysis question and an answer, and includes explanations of control flow, execution order, and timing relationships. It supports code SFT training and evaluation for understanding scheduling implementations in co-simulation tools, rather than generating or configuring simulation models.
13
+
14
+ ## Technical Specifications
15
+
16
+ | Field | Type | Description |
17
+ | :--- | :--- | :--- |
18
+ | source_code | string | Source code from a co-simulation master controller or scheduling component to be analyzed. |
19
+ | execution_order | array | An ordered list of co-simulation components or scheduling stages, with an explanation of each stage. |
20
+ | analysis_question | string | A code understanding task or analysis question about the source code. |
21
+ | understanding_answer | string | An accurate answer based on the source code that explains the scheduling implementation and its key behaviors. |
22
+ | control_flow_explanation | string | An explanation of the call path, branch conditions, loop behavior, and changes in control flow across scheduling-related functions or modules. |
23
+ | timing_and_synchronization_explanation | string | An explanation of simulation step sizes, time advancement methods, synchronization conditions, and timing relationships between components. |
24
+
25
+ ## Compliance Statement
26
+
27
+ <table>
28
+ <tr><td>Authorization Type</td><td>CC-BY-NC-SA 4.0 (Attribution–NonCommercial–ShareAlike)</td></tr>
29
+ <tr><td>Commercial Use</td><td>Requires exclusive subscription or authorization contract (monthly or per-invocation charging)</td></tr>
30
+ <tr><td>Privacy and Anonymization</td><td>No PII, no real company names, simulated scenarios follow industry standards</td></tr>
31
+ <tr><td>Compliance System</td><td>Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs</td></tr>
32
+ </table>
33
+
34
+
35
+ ## Source & Contact
36
+
37
+ contact@mobiusi.com
38
+