Datasets:
[+] Init commit
Browse files- .gitattributes +9 -0
- LICENSE +395 -0
- README.md +186 -0
- figures/task 1.svg +1 -0
- figures/task 2.svg +1 -0
- figures/task 3.svg +1 -0
- figures/task 4.svg +1 -0
- figures/task 5.svg +0 -0
- figures/task 6.svg +1 -0
- task_1/topological_path_test.json +3 -0
- task_2/topological_connectivity_test.json +3 -0
- task_3/physical_test.json +3 -0
- task_4/counterfactual_test.json +3 -0
- task_5/agentic_test.json +0 -0
- task_6/opf_pglib_opf_case118_ieee_test.json +3 -0
- task_6/opf_pglib_opf_case14_ieee_test.json +3 -0
- task_6/opf_pglib_opf_case30_ieee_test.json +3 -0
- task_7/ctu_test.json +3 -0
- task_7/lcld_test.json +3 -0
- task_7/url_test.json +0 -0
.gitattributes
CHANGED
|
@@ -58,3 +58,12 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
|
|
| 58 |
# Video files - compressed
|
| 59 |
*.mp4 filter=lfs diff=lfs merge=lfs -text
|
| 60 |
*.webm filter=lfs diff=lfs merge=lfs -text
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 58 |
# Video files - compressed
|
| 59 |
*.mp4 filter=lfs diff=lfs merge=lfs -text
|
| 60 |
*.webm filter=lfs diff=lfs merge=lfs -text
|
| 61 |
+
task_1/topological_path_test.json filter=lfs diff=lfs merge=lfs -text
|
| 62 |
+
task_2/topological_connectivity_test.json filter=lfs diff=lfs merge=lfs -text
|
| 63 |
+
task_3/physical_test.json filter=lfs diff=lfs merge=lfs -text
|
| 64 |
+
task_4/counterfactual_test.json filter=lfs diff=lfs merge=lfs -text
|
| 65 |
+
task_6/opf_pglib_opf_case118_ieee_test.json filter=lfs diff=lfs merge=lfs -text
|
| 66 |
+
task_6/opf_pglib_opf_case14_ieee_test.json filter=lfs diff=lfs merge=lfs -text
|
| 67 |
+
task_6/opf_pglib_opf_case30_ieee_test.json filter=lfs diff=lfs merge=lfs -text
|
| 68 |
+
task_7/ctu_test.json filter=lfs diff=lfs merge=lfs -text
|
| 69 |
+
task_7/lcld_test.json filter=lfs diff=lfs merge=lfs -text
|
LICENSE
ADDED
|
@@ -0,0 +1,395 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
Attribution 4.0 International
|
| 2 |
+
|
| 3 |
+
=======================================================================
|
| 4 |
+
|
| 5 |
+
Creative Commons Corporation ("Creative Commons") is not a law firm and
|
| 6 |
+
does not provide legal services or legal advice. Distribution of
|
| 7 |
+
Creative Commons public licenses does not create a lawyer-client or
|
| 8 |
+
other relationship. Creative Commons makes its licenses and related
|
| 9 |
+
information available on an "as-is" basis. Creative Commons gives no
|
| 10 |
+
warranties regarding its licenses, any material licensed under their
|
| 11 |
+
terms and conditions, or any related information. Creative Commons
|
| 12 |
+
disclaims all liability for damages resulting from their use to the
|
| 13 |
+
fullest extent possible.
|
| 14 |
+
|
| 15 |
+
Using Creative Commons Public Licenses
|
| 16 |
+
|
| 17 |
+
Creative Commons public licenses provide a standard set of terms and
|
| 18 |
+
conditions that creators and other rights holders may use to share
|
| 19 |
+
original works of authorship and other material subject to copyright
|
| 20 |
+
and certain other rights specified in the public license below. The
|
| 21 |
+
following considerations are for informational purposes only, are not
|
| 22 |
+
exhaustive, and do not form part of our licenses.
|
| 23 |
+
|
| 24 |
+
Considerations for licensors: Our public licenses are
|
| 25 |
+
intended for use by those authorized to give the public
|
| 26 |
+
permission to use material in ways otherwise restricted by
|
| 27 |
+
copyright and certain other rights. Our licenses are
|
| 28 |
+
irrevocable. Licensors should read and understand the terms
|
| 29 |
+
and conditions of the license they choose before applying it.
|
| 30 |
+
Licensors should also secure all rights necessary before
|
| 31 |
+
applying our licenses so that the public can reuse the
|
| 32 |
+
material as expected. Licensors should clearly mark any
|
| 33 |
+
material not subject to the license. This includes other CC-
|
| 34 |
+
licensed material, or material used under an exception or
|
| 35 |
+
limitation to copyright. More considerations for licensors:
|
| 36 |
+
wiki.creativecommons.org/Considerations_for_licensors
|
| 37 |
+
|
| 38 |
+
Considerations for the public: By using one of our public
|
| 39 |
+
licenses, a licensor grants the public permission to use the
|
| 40 |
+
licensed material under specified terms and conditions. If
|
| 41 |
+
the licensor's permission is not necessary for any reason--for
|
| 42 |
+
example, because of any applicable exception or limitation to
|
| 43 |
+
copyright--then that use is not regulated by the license. Our
|
| 44 |
+
licenses grant only permissions under copyright and certain
|
| 45 |
+
other rights that a licensor has authority to grant. Use of
|
| 46 |
+
the licensed material may still be restricted for other
|
| 47 |
+
reasons, including because others have copyright or other
|
| 48 |
+
rights in the material. A licensor may make special requests,
|
| 49 |
+
such as asking that all changes be marked or described.
|
| 50 |
+
Although not required by our licenses, you are encouraged to
|
| 51 |
+
respect those requests where reasonable. More_considerations
|
| 52 |
+
for the public:
|
| 53 |
+
wiki.creativecommons.org/Considerations_for_licensees
|
| 54 |
+
|
| 55 |
+
=======================================================================
|
| 56 |
+
|
| 57 |
+
Creative Commons Attribution 4.0 International Public License
|
| 58 |
+
|
| 59 |
+
By exercising the Licensed Rights (defined below), You accept and agree
|
| 60 |
+
to be bound by the terms and conditions of this Creative Commons
|
| 61 |
+
Attribution 4.0 International Public License ("Public License"). To the
|
| 62 |
+
extent this Public License may be interpreted as a contract, You are
|
| 63 |
+
granted the Licensed Rights in consideration of Your acceptance of
|
| 64 |
+
these terms and conditions, and the Licensor grants You such rights in
|
| 65 |
+
consideration of benefits the Licensor receives from making the
|
| 66 |
+
Licensed Material available under these terms and conditions.
|
| 67 |
+
|
| 68 |
+
|
| 69 |
+
Section 1 -- Definitions.
|
| 70 |
+
|
| 71 |
+
a. Adapted Material means material subject to Copyright and Similar
|
| 72 |
+
Rights that is derived from or based upon the Licensed Material
|
| 73 |
+
and in which the Licensed Material is translated, altered,
|
| 74 |
+
arranged, transformed, or otherwise modified in a manner requiring
|
| 75 |
+
permission under the Copyright and Similar Rights held by the
|
| 76 |
+
Licensor. For purposes of this Public License, where the Licensed
|
| 77 |
+
Material is a musical work, performance, or sound recording,
|
| 78 |
+
Adapted Material is always produced where the Licensed Material is
|
| 79 |
+
synched in timed relation with a moving image.
|
| 80 |
+
|
| 81 |
+
b. Adapter's License means the license You apply to Your Copyright
|
| 82 |
+
and Similar Rights in Your contributions to Adapted Material in
|
| 83 |
+
accordance with the terms and conditions of this Public License.
|
| 84 |
+
|
| 85 |
+
c. Copyright and Similar Rights means copyright and/or similar rights
|
| 86 |
+
closely related to copyright including, without limitation,
|
| 87 |
+
performance, broadcast, sound recording, and Sui Generis Database
|
| 88 |
+
Rights, without regard to how the rights are labeled or
|
| 89 |
+
categorized. For purposes of this Public License, the rights
|
| 90 |
+
specified in Section 2(b)(1)-(2) are not Copyright and Similar
|
| 91 |
+
Rights.
|
| 92 |
+
|
| 93 |
+
d. Effective Technological Measures means those measures that, in the
|
| 94 |
+
absence of proper authority, may not be circumvented under laws
|
| 95 |
+
fulfilling obligations under Article 11 of the WIPO Copyright
|
| 96 |
+
Treaty adopted on December 20, 1996, and/or similar international
|
| 97 |
+
agreements.
|
| 98 |
+
|
| 99 |
+
e. Exceptions and Limitations means fair use, fair dealing, and/or
|
| 100 |
+
any other exception or limitation to Copyright and Similar Rights
|
| 101 |
+
that applies to Your use of the Licensed Material.
|
| 102 |
+
|
| 103 |
+
f. Licensed Material means the artistic or literary work, database,
|
| 104 |
+
or other material to which the Licensor applied this Public
|
| 105 |
+
License.
|
| 106 |
+
|
| 107 |
+
g. Licensed Rights means the rights granted to You subject to the
|
| 108 |
+
terms and conditions of this Public License, which are limited to
|
| 109 |
+
all Copyright and Similar Rights that apply to Your use of the
|
| 110 |
+
Licensed Material and that the Licensor has authority to license.
|
| 111 |
+
|
| 112 |
+
h. Licensor means the individual(s) or entity(ies) granting rights
|
| 113 |
+
under this Public License.
|
| 114 |
+
|
| 115 |
+
i. Share means to provide material to the public by any means or
|
| 116 |
+
process that requires permission under the Licensed Rights, such
|
| 117 |
+
as reproduction, public display, public performance, distribution,
|
| 118 |
+
dissemination, communication, or importation, and to make material
|
| 119 |
+
available to the public including in ways that members of the
|
| 120 |
+
public may access the material from a place and at a time
|
| 121 |
+
individually chosen by them.
|
| 122 |
+
|
| 123 |
+
j. Sui Generis Database Rights means rights other than copyright
|
| 124 |
+
resulting from Directive 96/9/EC of the European Parliament and of
|
| 125 |
+
the Council of 11 March 1996 on the legal protection of databases,
|
| 126 |
+
as amended and/or succeeded, as well as other essentially
|
| 127 |
+
equivalent rights anywhere in the world.
|
| 128 |
+
|
| 129 |
+
k. You means the individual or entity exercising the Licensed Rights
|
| 130 |
+
under this Public License. Your has a corresponding meaning.
|
| 131 |
+
|
| 132 |
+
|
| 133 |
+
Section 2 -- Scope.
|
| 134 |
+
|
| 135 |
+
a. License grant.
|
| 136 |
+
|
| 137 |
+
1. Subject to the terms and conditions of this Public License,
|
| 138 |
+
the Licensor hereby grants You a worldwide, royalty-free,
|
| 139 |
+
non-sublicensable, non-exclusive, irrevocable license to
|
| 140 |
+
exercise the Licensed Rights in the Licensed Material to:
|
| 141 |
+
|
| 142 |
+
a. reproduce and Share the Licensed Material, in whole or
|
| 143 |
+
in part; and
|
| 144 |
+
|
| 145 |
+
b. produce, reproduce, and Share Adapted Material.
|
| 146 |
+
|
| 147 |
+
2. Exceptions and Limitations. For the avoidance of doubt, where
|
| 148 |
+
Exceptions and Limitations apply to Your use, this Public
|
| 149 |
+
License does not apply, and You do not need to comply with
|
| 150 |
+
its terms and conditions.
|
| 151 |
+
|
| 152 |
+
3. Term. The term of this Public License is specified in Section
|
| 153 |
+
6(a).
|
| 154 |
+
|
| 155 |
+
4. Media and formats; technical modifications allowed. The
|
| 156 |
+
Licensor authorizes You to exercise the Licensed Rights in
|
| 157 |
+
all media and formats whether now known or hereafter created,
|
| 158 |
+
and to make technical modifications necessary to do so. The
|
| 159 |
+
Licensor waives and/or agrees not to assert any right or
|
| 160 |
+
authority to forbid You from making technical modifications
|
| 161 |
+
necessary to exercise the Licensed Rights, including
|
| 162 |
+
technical modifications necessary to circumvent Effective
|
| 163 |
+
Technological Measures. For purposes of this Public License,
|
| 164 |
+
simply making modifications authorized by this Section 2(a)
|
| 165 |
+
(4) never produces Adapted Material.
|
| 166 |
+
|
| 167 |
+
5. Downstream recipients.
|
| 168 |
+
|
| 169 |
+
a. Offer from the Licensor -- Licensed Material. Every
|
| 170 |
+
recipient of the Licensed Material automatically
|
| 171 |
+
receives an offer from the Licensor to exercise the
|
| 172 |
+
Licensed Rights under the terms and conditions of this
|
| 173 |
+
Public License.
|
| 174 |
+
|
| 175 |
+
b. No downstream restrictions. You may not offer or impose
|
| 176 |
+
any additional or different terms or conditions on, or
|
| 177 |
+
apply any Effective Technological Measures to, the
|
| 178 |
+
Licensed Material if doing so restricts exercise of the
|
| 179 |
+
Licensed Rights by any recipient of the Licensed
|
| 180 |
+
Material.
|
| 181 |
+
|
| 182 |
+
6. No endorsement. Nothing in this Public License constitutes or
|
| 183 |
+
may be construed as permission to assert or imply that You
|
| 184 |
+
are, or that Your use of the Licensed Material is, connected
|
| 185 |
+
with, or sponsored, endorsed, or granted official status by,
|
| 186 |
+
the Licensor or others designated to receive attribution as
|
| 187 |
+
provided in Section 3(a)(1)(A)(i).
|
| 188 |
+
|
| 189 |
+
b. Other rights.
|
| 190 |
+
|
| 191 |
+
1. Moral rights, such as the right of integrity, are not
|
| 192 |
+
licensed under this Public License, nor are publicity,
|
| 193 |
+
privacy, and/or other similar personality rights; however, to
|
| 194 |
+
the extent possible, the Licensor waives and/or agrees not to
|
| 195 |
+
assert any such rights held by the Licensor to the limited
|
| 196 |
+
extent necessary to allow You to exercise the Licensed
|
| 197 |
+
Rights, but not otherwise.
|
| 198 |
+
|
| 199 |
+
2. Patent and trademark rights are not licensed under this
|
| 200 |
+
Public License.
|
| 201 |
+
|
| 202 |
+
3. To the extent possible, the Licensor waives any right to
|
| 203 |
+
collect royalties from You for the exercise of the Licensed
|
| 204 |
+
Rights, whether directly or through a collecting society
|
| 205 |
+
under any voluntary or waivable statutory or compulsory
|
| 206 |
+
licensing scheme. In all other cases the Licensor expressly
|
| 207 |
+
reserves any right to collect such royalties.
|
| 208 |
+
|
| 209 |
+
|
| 210 |
+
Section 3 -- License Conditions.
|
| 211 |
+
|
| 212 |
+
Your exercise of the Licensed Rights is expressly made subject to the
|
| 213 |
+
following conditions.
|
| 214 |
+
|
| 215 |
+
a. Attribution.
|
| 216 |
+
|
| 217 |
+
1. If You Share the Licensed Material (including in modified
|
| 218 |
+
form), You must:
|
| 219 |
+
|
| 220 |
+
a. retain the following if it is supplied by the Licensor
|
| 221 |
+
with the Licensed Material:
|
| 222 |
+
|
| 223 |
+
i. identification of the creator(s) of the Licensed
|
| 224 |
+
Material and any others designated to receive
|
| 225 |
+
attribution, in any reasonable manner requested by
|
| 226 |
+
the Licensor (including by pseudonym if
|
| 227 |
+
designated);
|
| 228 |
+
|
| 229 |
+
ii. a copyright notice;
|
| 230 |
+
|
| 231 |
+
iii. a notice that refers to this Public License;
|
| 232 |
+
|
| 233 |
+
iv. a notice that refers to the disclaimer of
|
| 234 |
+
warranties;
|
| 235 |
+
|
| 236 |
+
v. a URI or hyperlink to the Licensed Material to the
|
| 237 |
+
extent reasonably practicable;
|
| 238 |
+
|
| 239 |
+
b. indicate if You modified the Licensed Material and
|
| 240 |
+
retain an indication of any previous modifications; and
|
| 241 |
+
|
| 242 |
+
c. indicate the Licensed Material is licensed under this
|
| 243 |
+
Public License, and include the text of, or the URI or
|
| 244 |
+
hyperlink to, this Public License.
|
| 245 |
+
|
| 246 |
+
2. You may satisfy the conditions in Section 3(a)(1) in any
|
| 247 |
+
reasonable manner based on the medium, means, and context in
|
| 248 |
+
which You Share the Licensed Material. For example, it may be
|
| 249 |
+
reasonable to satisfy the conditions by providing a URI or
|
| 250 |
+
hyperlink to a resource that includes the required
|
| 251 |
+
information.
|
| 252 |
+
|
| 253 |
+
3. If requested by the Licensor, You must remove any of the
|
| 254 |
+
information required by Section 3(a)(1)(A) to the extent
|
| 255 |
+
reasonably practicable.
|
| 256 |
+
|
| 257 |
+
4. If You Share Adapted Material You produce, the Adapter's
|
| 258 |
+
License You apply must not prevent recipients of the Adapted
|
| 259 |
+
Material from complying with this Public License.
|
| 260 |
+
|
| 261 |
+
|
| 262 |
+
Section 4 -- Sui Generis Database Rights.
|
| 263 |
+
|
| 264 |
+
Where the Licensed Rights include Sui Generis Database Rights that
|
| 265 |
+
apply to Your use of the Licensed Material:
|
| 266 |
+
|
| 267 |
+
a. for the avoidance of doubt, Section 2(a)(1) grants You the right
|
| 268 |
+
to extract, reuse, reproduce, and Share all or a substantial
|
| 269 |
+
portion of the contents of the database;
|
| 270 |
+
|
| 271 |
+
b. if You include all or a substantial portion of the database
|
| 272 |
+
contents in a database in which You have Sui Generis Database
|
| 273 |
+
Rights, then the database in which You have Sui Generis Database
|
| 274 |
+
Rights (but not its individual contents) is Adapted Material; and
|
| 275 |
+
|
| 276 |
+
c. You must comply with the conditions in Section 3(a) if You Share
|
| 277 |
+
all or a substantial portion of the contents of the database.
|
| 278 |
+
|
| 279 |
+
For the avoidance of doubt, this Section 4 supplements and does not
|
| 280 |
+
replace Your obligations under this Public License where the Licensed
|
| 281 |
+
Rights include other Copyright and Similar Rights.
|
| 282 |
+
|
| 283 |
+
|
| 284 |
+
Section 5 -- Disclaimer of Warranties and Limitation of Liability.
|
| 285 |
+
|
| 286 |
+
a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
|
| 287 |
+
EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
|
| 288 |
+
AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
|
| 289 |
+
ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
|
| 290 |
+
IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
|
| 291 |
+
WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
|
| 292 |
+
PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
|
| 293 |
+
ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
|
| 294 |
+
KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
|
| 295 |
+
ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.
|
| 296 |
+
|
| 297 |
+
b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
|
| 298 |
+
TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
|
| 299 |
+
NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
|
| 300 |
+
INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
|
| 301 |
+
COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
|
| 302 |
+
USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
|
| 303 |
+
ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
|
| 304 |
+
DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
|
| 305 |
+
IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.
|
| 306 |
+
|
| 307 |
+
c. The disclaimer of warranties and limitation of liability provided
|
| 308 |
+
above shall be interpreted in a manner that, to the extent
|
| 309 |
+
possible, most closely approximates an absolute disclaimer and
|
| 310 |
+
waiver of all liability.
|
| 311 |
+
|
| 312 |
+
|
| 313 |
+
Section 6 -- Term and Termination.
|
| 314 |
+
|
| 315 |
+
a. This Public License applies for the term of the Copyright and
|
| 316 |
+
Similar Rights licensed here. However, if You fail to comply with
|
| 317 |
+
this Public License, then Your rights under this Public License
|
| 318 |
+
terminate automatically.
|
| 319 |
+
|
| 320 |
+
b. Where Your right to use the Licensed Material has terminated under
|
| 321 |
+
Section 6(a), it reinstates:
|
| 322 |
+
|
| 323 |
+
1. automatically as of the date the violation is cured, provided
|
| 324 |
+
it is cured within 30 days of Your discovery of the
|
| 325 |
+
violation; or
|
| 326 |
+
|
| 327 |
+
2. upon express reinstatement by the Licensor.
|
| 328 |
+
|
| 329 |
+
For the avoidance of doubt, this Section 6(b) does not affect any
|
| 330 |
+
right the Licensor may have to seek remedies for Your violations
|
| 331 |
+
of this Public License.
|
| 332 |
+
|
| 333 |
+
c. For the avoidance of doubt, the Licensor may also offer the
|
| 334 |
+
Licensed Material under separate terms or conditions or stop
|
| 335 |
+
distributing the Licensed Material at any time; however, doing so
|
| 336 |
+
will not terminate this Public License.
|
| 337 |
+
|
| 338 |
+
d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
|
| 339 |
+
License.
|
| 340 |
+
|
| 341 |
+
|
| 342 |
+
Section 7 -- Other Terms and Conditions.
|
| 343 |
+
|
| 344 |
+
a. The Licensor shall not be bound by any additional or different
|
| 345 |
+
terms or conditions communicated by You unless expressly agreed.
|
| 346 |
+
|
| 347 |
+
b. Any arrangements, understandings, or agreements regarding the
|
| 348 |
+
Licensed Material not stated herein are separate from and
|
| 349 |
+
independent of the terms and conditions of this Public License.
|
| 350 |
+
|
| 351 |
+
|
| 352 |
+
Section 8 -- Interpretation.
|
| 353 |
+
|
| 354 |
+
a. For the avoidance of doubt, this Public License does not, and
|
| 355 |
+
shall not be interpreted to, reduce, limit, restrict, or impose
|
| 356 |
+
conditions on any use of the Licensed Material that could lawfully
|
| 357 |
+
be made without permission under this Public License.
|
| 358 |
+
|
| 359 |
+
b. To the extent possible, if any provision of this Public License is
|
| 360 |
+
deemed unenforceable, it shall be automatically reformed to the
|
| 361 |
+
minimum extent necessary to make it enforceable. If the provision
|
| 362 |
+
cannot be reformed, it shall be severed from this Public License
|
| 363 |
+
without affecting the enforceability of the remaining terms and
|
| 364 |
+
conditions.
|
| 365 |
+
|
| 366 |
+
c. No term or condition of this Public License will be waived and no
|
| 367 |
+
failure to comply consented to unless expressly agreed to by the
|
| 368 |
+
Licensor.
|
| 369 |
+
|
| 370 |
+
d. Nothing in this Public License constitutes or may be interpreted
|
| 371 |
+
as a limitation upon, or waiver of, any privileges and immunities
|
| 372 |
+
that apply to the Licensor or You, including from the legal
|
| 373 |
+
processes of any jurisdiction or authority.
|
| 374 |
+
|
| 375 |
+
|
| 376 |
+
=======================================================================
|
| 377 |
+
|
| 378 |
+
Creative Commons is not a party to its public
|
| 379 |
+
licenses. Notwithstanding, Creative Commons may elect to apply one of
|
| 380 |
+
its public licenses to material it publishes and in those instances
|
| 381 |
+
will be considered the “Licensor.” The text of the Creative Commons
|
| 382 |
+
public licenses is dedicated to the public domain under the CC0 Public
|
| 383 |
+
Domain Dedication. Except for the limited purpose of indicating that
|
| 384 |
+
material is shared under a Creative Commons public license or as
|
| 385 |
+
otherwise permitted by the Creative Commons policies published at
|
| 386 |
+
creativecommons.org/policies, Creative Commons does not authorize the
|
| 387 |
+
use of the trademark "Creative Commons" or any other trademark or logo
|
| 388 |
+
of Creative Commons without its prior written consent including,
|
| 389 |
+
without limitation, in connection with any unauthorized modifications
|
| 390 |
+
to any of its public licenses or any other arrangements,
|
| 391 |
+
understandings, or agreements concerning use of licensed material. For
|
| 392 |
+
the avoidance of doubt, this paragraph does not form part of the
|
| 393 |
+
public licenses.
|
| 394 |
+
|
| 395 |
+
Creative Commons may be contacted at creativecommons.org.
|
README.md
ADDED
|
@@ -0,0 +1,186 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# ORC-bench
|
| 2 |
+
|
| 3 |
+
| Task 1: Topological Path Finding | Task 2: Topological Connectivity | Task 3: Linear Power Flow |
|
| 4 |
+
|---|---|---|
|
| 5 |
+
|  |  |  |
|
| 6 |
+
|
| 7 |
+
| Task 4: Contingency Analysis | Task 5: Power Grid Control | Task 6: Power Flow Optimization |
|
| 8 |
+
|---|---|---|
|
| 9 |
+
|  |  |  |
|
| 10 |
+
|
| 11 |
+
|
| 12 |
+
## Task 1: Topological Path Finding
|
| 13 |
+
|
| 14 |
+
### Problem Formulation
|
| 15 |
+
This task assesses the spatial reasoning ability of the model by asking it to determine the shortest path between two specific buses in a given power grid state. The grid state may include modifications, such as the temporary removal of transmission lines, requiring the model to dynamically reason over the provided text-based topology rather than relying on memorized standard grid structures.
|
| 16 |
+
|
| 17 |
+
### Dataset Generation
|
| 18 |
+
The dataset is generated using standard Institute of Electrical and Electronics Engineers (IEEE) 14, 30, and 118 bus cases. To ensure diversity and require active reasoning, up to 2 unique lines (for IEEE 14) or 5 unique lines (for larger cases) are randomly removed. A NetworkX MultiGraph is constructed using the remaining operational lines (buses can be connected by more than 1 line in IEEE 118). Two random buses are selected as the source and target. The `all_shortest_paths` algorithm is used to compute the valid paths. If a path exists, the ground truth is formatted as a sequence of nodes (e.g., `Bus A -> Bus B -> Bus C`); if none exists, the answer is `No path exists.`
|
| 19 |
+
|
| 20 |
+
### LLM Evaluation
|
| 21 |
+
The LLM is provided with the textual representation of the grid topology (including the base system and any offline lines) and the query asking for the shortest path.
|
| 22 |
+
|
| 23 |
+
**System Prompt:**
|
| 24 |
+
> *You are a power systems expert. Provide the shortest path between the requested buses in the following format including the starting and ending buses: Bus A -> Bus B -> Bus C. If no path exists, respond with 'No path exists.' Do not provide any other text.*
|
| 25 |
+
|
| 26 |
+
### Performance Metrics
|
| 27 |
+
Performance is evaluated using an exact path-matching algorithm. To prevent false positives from partial matches (e.g., predicting “Bus 22” when the ground truth is “Bus 2”), the evaluation script enforces strict alphanumeric word boundaries when searching for the ground truth path within the model's output. The primary metric is **Accuracy**, computed both overall and per IEEE case.
|
| 28 |
+
|
| 29 |
+
---
|
| 30 |
+
|
| 31 |
+
## Task 2: Topological Connectivity
|
| 32 |
+
|
| 33 |
+
### Problem Formulation
|
| 34 |
+
This task evaluates the model's ability to deduce graph connectivity. The model must determine whether a path exists between two specific buses in a degraded power grid, effectively answering a binary “Yes” or “No” question based on the textual grid description.
|
| 35 |
+
|
| 36 |
+
### Dataset Generation
|
| 37 |
+
Similar to Task 1a, the dataset is generated using **Python** and **NetworkX**, built upon IEEE 14, 30, and 118 bus networks. Up to 5 edges are randomly removed from the base graph to create disconnected subgraphs or alternate routes. Two random buses are sampled, and the `networkx.has_path` function determines the ground truth connectivity state (“Yes” or “No”). The textual prompt lists the offline lines.
|
| 38 |
+
|
| 39 |
+
### LLM Evaluation
|
| 40 |
+
The model is prompted with the grid state and asked a direct question: “Is [Start Bus] connected to [End Bus]?” The exact system prompt used is:
|
| 41 |
+
|
| 42 |
+
> *You are a power systems expert. Determine if two buses are connected. Respond only with 'Yes' or 'No'. Do not provide any other text.*
|
| 43 |
+
|
| 44 |
+
### Performance Metrics
|
| 45 |
+
The metric for this task is binary **Accuracy**. The model's predicted response is compared against the ground truth using a case-insensitive exact match. Accuracy is reported across the entire dataset as well as per grid case.
|
| 46 |
+
|
| 47 |
+
---
|
| 48 |
+
|
| 49 |
+
## Task 3: Linear Power Flow
|
| 50 |
+
|
| 51 |
+
### Problem Formulation
|
| 52 |
+
This task transitions from topological to physical reasoning by asking the model to calculate the active power flow (in Megawatts \[MW]) on a specific transmission line. This tests the LLM's capability to understand electrical parameters and perform implicit physical calculations or heuristics based on grid state descriptions.
|
| 53 |
+
|
| 54 |
+
### Dataset Generation
|
| 55 |
+
The dataset is generated using **Python** and the **PyPSA** (Python for Power System Analysis) library. It uses IEEE 14, 30, and 118 bus systems. To create unique scenarios, the active power load (`p_set`) and generator capacities (`p_nom`) are randomized uniformly between 80% and 120% of their base values. A Direct Current (DC) linear power flow (LPF) is solved using PyPSA's `network.lpf()` solver to obtain the steady-state active power flows. A target line is randomly chosen, and its simulated flow (rounded to two decimal places) is recorded as the ground truth.
|
| 56 |
+
|
| 57 |
+
### LLM Evaluation
|
| 58 |
+
The model is provided with the complete, randomized grid state (including node injections) and asked: “What is the active power flow (MW) on [Target Line]?” The exact system prompt used is:
|
| 59 |
+
|
| 60 |
+
> *You are a power systems expert. Calculate the requested physical value (e.g., Power in MW). Respond only with the numerical value. Do not provide units or any other text.*
|
| 61 |
+
|
| 62 |
+
### Performance Metrics
|
| 63 |
+
Because the output is continuous, performance is measured using **Mean Absolute Error (MAE)** and **Root Mean Square Error (RMSE)**. A regular expression extracts the first floating-point number from the model's response to compare against the ground truth flow.
|
| 64 |
+
|
| 65 |
+
---
|
| 66 |
+
|
| 67 |
+
## Task 4: Contingency Analysis
|
| 68 |
+
|
| 69 |
+
### Problem Formulation
|
| 70 |
+
This task tests N-1 (N minus one) contingency analysis and counterfactual reasoning. Given a base grid state and a scenario describing the sudden loss of a generator or transmission line, the model must identify the transmission line most likely to overload (experience the highest flow increase) and provide a logical explanation for its choice.
|
| 71 |
+
|
| 72 |
+
### Dataset Generation
|
| 73 |
+
The dataset is generated using **PyPSA**. Base flows are calculated for IEEE 14, 30, and 118 cases using the PyPSA Linear Power Flow (LPF) solver. A random N-1 contingency is applied programmatically: either a non-slack generator is tripped (output set to 0), or a transmission line is removed. The system is re-solved, and the absolute difference in line flows is calculated to find the line with the maximum spike. The dataset includes a Chain-of-Thought (CoT) answer that explains the lost element, the rerouting of power, and the identification of the overloaded line.
|
| 74 |
+
|
| 75 |
+
### LLM Evaluation
|
| 76 |
+
The model receives the grid state and the contingency scenario. It must predict the overloaded line and justify it. The exact system prompt used is:
|
| 77 |
+
|
| 78 |
+
> *You are a power systems expert. Provide the line ID of the most likely overloaded transmission line in double brackets (e.g., \[\[L0\]\] for line 0) and then provide a step-by-step explanation.*
|
| 79 |
+
|
| 80 |
+
### Performance Metrics
|
| 81 |
+
The primary metric is **Accuracy** of identifying the correct overloaded line. Evaluation is performed by verifying if the ground truth target line string is explicitly mentioned within the predicted response.
|
| 82 |
+
|
| 83 |
+
---
|
| 84 |
+
|
| 85 |
+
## Task 5: Power Grid Control
|
| 86 |
+
|
| 87 |
+
### Problem Formulation
|
| 88 |
+
This task assesses the model's ability to act as a grid operator (agent). Given a set of system telemetry readings (frequency drop and voltage levels) and a sudden disturbance (e.g., wind generation drop), the model must choose the best corrective action from a multiple-choice list.
|
| 89 |
+
|
| 90 |
+
### Dataset Generation
|
| 91 |
+
The dataset is generated using **Python**'s standard libraries to simulate telemetry logic. For IEEE systems, 1,500 scenarios are generated representing four states: critical frequency drop, moderate frequency drop, low voltage, or stable system. Random telemetry parameters are generated within specific bounds for each state (e.g., critical frequency is between 49.0 and 49.49 Hz). Ground truth actions are deterministically mapped to the scenarios (e.g., a critical frequency drop requires spinning up a gas turbine).
|
| 92 |
+
|
| 93 |
+
### LLM Evaluation
|
| 94 |
+
The model is prompted with the grid state, telemetry data, and four possible actions (A, B, C, D). The exact system prompt used is:
|
| 95 |
+
|
| 96 |
+
> *You are a power grid operator. Based on the telemetry provided, select the most appropriate control action from the given choices. Respond by providing the choice label in brackets, e.g., \[B\].*
|
| 97 |
+
|
| 98 |
+
### Performance Metrics
|
| 99 |
+
The metric is **Accuracy**, calculated by checking whether the correct textual explanation or the correct action bracket (e.g., `[B]`) is present within the model's lowercased prediction string.
|
| 100 |
+
|
| 101 |
+
---
|
| 102 |
+
|
| 103 |
+
## Task 6: Optimal Power Flow Optimization
|
| 104 |
+
|
| 105 |
+
### Problem Formulation
|
| 106 |
+
This task represents the most complex numerical reasoning challenge, assessing the model's ability to act as an end-to-end mathematical solver for the Optimal Power Flow (OPF) problem. Given a serialized heterogeneous graph representation of a power grid—including buses, loads, generators, and transmission lines—the model must compute the optimal operating state. This requires balancing complex non-linear physical constraints (Kirchhoff's laws) and operational limits (voltage bounds, generator capacities) to determine active and reactive power injections and bus voltage magnitudes and angles.
|
| 107 |
+
|
| 108 |
+
### Dataset Generation
|
| 109 |
+
The dataset is procedurally generated using **PyTorch Geometric (PyG)** library. Specifically, we are curating and adapting the `OPFDataset` used for traditional GNN evaluation for a LLM setting. Complex grid topologies are parsed into a heterogeneous graph format, which is then serialized into structured JSON dictionaries mapping node features and edge indices. To facilitate in-context learning, few-shot prompt examples are constructed, pairing an “Example Input JSON” with its corresponding solved “Example Output JSON”.
|
| 110 |
+
|
| 111 |
+
### LLM Evaluation
|
| 112 |
+
The model is prompted with the system instructions, the few-shot examples, and a final “Query Input JSON” that it must solve. The exact system prompt used is:
|
| 113 |
+
|
| 114 |
+
> *You are a powergrid operator running Optimal Power Flow simulation and you need to return a JSON formatted responses based on the provided input JSON. The input is the description of the components of the grid, including the buses, generators, loads, lines, and external grid. The output is the solution to the optimal power flow problem. You will get a few examples of Input and Output json. You need to return the correct Output for the last given Input*
|
| 115 |
+
|
| 116 |
+
A robust regex-based extraction script parses the model's text output to isolate the final predicted JSON object.
|
| 117 |
+
|
| 118 |
+
### Performance Metrics
|
| 119 |
+
- **Constraints:** We evaluate each predicted OPF solution using three feasibility criteria. For every bus (i), we compute the active and reactive power-balance residuals
|
| 120 |
+
\(\Delta P_i = P_i^{\mathrm{spec}} - P_i^{\mathrm{imp}}\) and \(\Delta Q_i = Q_i^{\mathrm{spec}} - Q_i^{\mathrm{imp}}\),
|
| 121 |
+
where the specified injections are given by the predicted generation minus demand, and the implied injections are those induced by the predicted bus voltages under the instance topology. A bus is deemed to satisfy the power-flow equations if:
|
| 122 |
+
|
| 123 |
+
\[
|
| 124 |
+
\sqrt{\Delta P_i^2 + \Delta Qi^2} \le \varepsilon{\mathrm{pf}}.
|
| 125 |
+
\]
|
| 126 |
+
|
| 127 |
+
Voltage feasibility is enforced via the bounds \(v_i^{\min} \le \hat v_i \le v_i^{\max}\), and generator feasibility via the active-power limits \(P_g^{\min} \le \hat P_g \le Pg^{\max}\).
|
| 128 |
+
|
| 129 |
+
For each sample, we compute the fraction of buses (or generators) that satisfy each condition, and report the dataset-level mean of these per-sample fractions. We additionally report an overall constraint satisfaction score obtained by micro-averaging all individual bus- and generator-level checks over the entire evaluation set, so that each constraint instance is weighted equally. Specifically, let (s) index evaluation samples, and let \(n{\mathrm{pf}}^{(s)}\), \(n{\mathrm{v}}^{(s)}\), and \(n{\mathrm{g}}^{(s)}\) denote the numbers of evaluated buses and generators for the power-flow, voltage, and generator constraints, with \(n{\mathrm{pf,sat}}^{(s)}\), \(n{\mathrm{v,sat}}^{(s)}\), and \(n_{\mathrm{g,sat}}^{(s)}\) the corresponding numbers satisfied.
|
| 130 |
+
|
| 131 |
+
- **MSE:** To evaluate the numerical accuracy of the predicted OPF solutions, we compute the Mean Squared Error (MSE) between the model outputs and the ground-truth solver results in the dataset. We report the total of two components: (i) a generator MSE, calculated over each generator's active and reactive power outputs, and (ii) a bus MSE, calculated over the voltage magnitude and voltage angle at each bus. In addition to constraint satisfaction, the MSE quantifies how closely the predictions match the optimal dispatch numerically.
|
| 132 |
+
|
| 133 |
+
- **Valid rate:** Tracks the model's ability to produce structurally correct JSON (can be parsed without raising error).
|
| 134 |
+
|
| 135 |
+
---
|
| 136 |
+
|
| 137 |
+
## Task 7-C: Credit Scoring
|
| 138 |
+
|
| 139 |
+
### Problem Formulation
|
| 140 |
+
This task assesses the model's ability to act as a financial expert to analyze loan application data and predict missing financial details. Given a structured tabular representation of an applicant's characteristics and loan parameters (in JSON format), the model must predict missing values such as installment, open accounts, bankruptcies, term, and various financial ratios. This evaluates the LLM's capability to reason over financial constraints and tabular data structures.
|
| 141 |
+
|
| 142 |
+
### Dataset Generation
|
| 143 |
+
The dataset is derived from the Lending Club Loan Data (LCLD) dataset. The objective is to predict the value of a dropped column that is involved in constrained relationship with other columns. For the few-shot in-context learning evaluation, multiple context examples are selected, where each example presents an “Example Input JSON” (containing applicant and loan features) and an “Example Output JSON” (containing the target financial columns). The target variables include continuous and discrete fields.
|
| 144 |
+
|
| 145 |
+
### LLM Evaluation
|
| 146 |
+
The model is prompted with the few-shot examples and asked to predict the target columns for a “Query Input JSON”. The exact system prompt used is:
|
| 147 |
+
|
| 148 |
+
> *You are a financial expert. Your task is to analyze the provided loan application data and predict the missing financial details. You need to return a JSON formatted response based on the provided input JSON. The input contains various applicant and loan characteristics. The output should contain the predicted missing values for specific fields such as installment, open accounts, bankruptcies, term, and various financial ratios. You will receive an Input JSON and you must return the correct Output JSON.*
|
| 149 |
+
|
| 150 |
+
### Performance Metrics
|
| 151 |
+
Evaluation is conducted using a constraints checker from the `TabularBench` framework. The primary quantitative metric is **Mean Squared Error (MSE)** between the predicted numerical values and the ground truth. Additionally, structural and logical validity is measured via the **Constraint Satisfaction (CTR)** metric, which checks if the predicted fields satisfy intrinsic tabular constraints and mathematical invariants defined by the dataset. The proportion of **Invalid JSON** responses is also tracked.
|
| 152 |
+
|
| 153 |
+
---
|
| 154 |
+
|
| 155 |
+
## Task 7-U: Phishing Detection
|
| 156 |
+
|
| 157 |
+
### Problem Formulation
|
| 158 |
+
This task tests the model's capability in cyber-security, specifically acting as an expert in phishing detection. The model is provided with characteristics extracted from a URL (e.g., in JSON format) and must predict missing security details, such as the length of the URL, number of “.com” domains, presence of HTTP in the path, ratio of digits in the URL and host, and number of redirections.
|
| 159 |
+
|
| 160 |
+
### Dataset Generation
|
| 161 |
+
The dataset is generated from a Phishing URL tabular dataset. A structured prompt is built containing a specific number of few-shot examples. Each example splits the tabular row into an input JSON containing URL characteristics and an output JSON holding the target security fields.
|
| 162 |
+
|
| 163 |
+
### LLM Evaluation
|
| 164 |
+
The model is evaluated on its ability to infer the missing URL characteristics from the given inputs. The exact system prompt used is:
|
| 165 |
+
|
| 166 |
+
> *You are a cyber-security expert in fishing detection. Your task is to analyze the provided URL data and predict the missing security details. You need to return a JSON formatted response based on the provided input JSON. The input contains various URL characteristics. The output should contain the predicted missing values for specific fields such as length_url, nb_com, http_in_path, ratio_digits_url, ratio_digits_host, and nb_redirection. You will receive an Input JSON and you must return the correct Output JSON.*
|
| 167 |
+
|
| 168 |
+
### Performance Metrics
|
| 169 |
+
The evaluation computes the **Mean Squared Error (MSE)** for continuous and discrete predicted URL properties. We also utilize the `tabularbench` constraints checker to report the **Constraint Satisfaction (CTR)** rate, ensuring that the model's output satisfies real-world data constraints (e.g., non-negative lengths and ratios). The **Invalid JSON** error rate is also measured to assess the structural formatting reliability of the LLM.
|
| 170 |
+
|
| 171 |
+
---
|
| 172 |
+
|
| 173 |
+
## Task 7-B: BOTNET detection
|
| 174 |
+
|
| 175 |
+
### Problem Formulation
|
| 176 |
+
This task assesses the model's proficiency in analyzing network traffic to identify botnet attacks. Acting as a cyber-security expert, the LLM analyzes a JSON representation of network traffic characteristics and must predict missing security details related to aggregated communication protocols (e.g., ICMP, UDP, TCP sums, byte flows, and durations).
|
| 177 |
+
|
| 178 |
+
### Dataset Generation
|
| 179 |
+
The dataset is processed from the CTU-13 NERIS tabular dataset using **Python** and **Pandas**. The data is partitioned, and a series of prompt contexts are generated. Each prompt includes multiple few-shot examples (“Example Input JSON” and “Example Output JSON”), isolating target columns like `icmp_sum_s_1`, `udp_sum_s_1`, `tcp_sum_s_1`, and byte/packet transfer sums from the rest of the network telemetry.
|
| 180 |
+
|
| 181 |
+
### LLM Evaluation
|
| 182 |
+
The LLM receives the prompt with few-shot network traffic examples and a target query. The exact system prompt used is:
|
| 183 |
+
> *You are a cyber-security expert in botnet attack detection. Your task is to analyze the provided network traffic data and predict the missing security details. You need to return a JSON formatted response based on the provided input JSON. The input contains various network traffic characteristics. The output should contain the predicted missing values for specific fields such as icmp_sum_s_1, udp_sum_s_1, tcp_sum_s_1, bytes_in_sum_d_2, bytes_out_sum_d_2, bytes_out_sum_s_1, pkts_out_sum_s_1, bytes_out_sum_d_3, pkts_out_sum_d_3, duration_max_d_1, and duration_max_s_OTHER. You will receive an Input JSON and you must return the correct Output JSON.*
|
| 184 |
+
|
| 185 |
+
### Performance Metrics
|
| 186 |
+
Performance is validated using the `TabularBench` framework. The predictions are scored using **Mean Squared Error (MSE)** against the ground truth ports values. A constraint satisfaction check calculates the **Constraint Satisfaction (CTR)** metric, which ensures that the interdependent packet and byte counts adhere to logical network constraints, alongside tracking the **Invalid JSON** structure rate.
|
figures/task 1.svg
ADDED
|
|
figures/task 2.svg
ADDED
|
|
figures/task 3.svg
ADDED
|
|
figures/task 4.svg
ADDED
|
|
figures/task 5.svg
ADDED
|
|
figures/task 6.svg
ADDED
|
|
task_1/topological_path_test.json
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:b07fef242644cfea8afdeaf8e9adecd71331dc0b85b625494f0e0a87c609090d
|
| 3 |
+
size 17487470
|
task_2/topological_connectivity_test.json
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:0484e46708b2b89cf1368d6e7f96e7d8f799511144453f4facf652761f688c01
|
| 3 |
+
size 16840750
|
task_3/physical_test.json
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:65ff3da0ca390100fa6ac24829ea1308bcb1a0994313b0a6788b839d88601ecd
|
| 3 |
+
size 16655185
|
task_4/counterfactual_test.json
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:7cf0e58128477085586314441ca4f120ba3e92ca5a4c0e461e71673200fa47a7
|
| 3 |
+
size 18578608
|
task_5/agentic_test.json
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|
task_6/opf_pglib_opf_case118_ieee_test.json
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:1347d1f4e371b31cdcbe9483331ec8d1842128e6c815c91d8ca53ac0c1fba424
|
| 3 |
+
size 175450487
|
task_6/opf_pglib_opf_case14_ieee_test.json
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:dbee301de6ba1420553c56bcfc703fdb87d3fde48cb01cab407b0bf353dbe3db
|
| 3 |
+
size 142810229
|
task_6/opf_pglib_opf_case30_ieee_test.json
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:c3171cdd830b6efae09552d446788bb834df475c53c388f2e69ef06f75887ea2
|
| 3 |
+
size 133940685
|
task_7/ctu_test.json
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:d35b186c3bb5874bd1ea7dadfc259c96cca5e36ac5fe37219a3ddee95bf6a62a
|
| 3 |
+
size 407728077
|
task_7/lcld_test.json
ADDED
|
@@ -0,0 +1,3 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:bdecac54b51b5ac3e2b4971580bdd7b86a3ef3c2a143788b87608ec8e100bacc
|
| 3 |
+
size 122011294
|
task_7/url_test.json
ADDED
|
The diff for this file is too large to render.
See raw diff
|
|
|