BaseNode
Bases: ABC
This abstract class is the base of all CRIPT nodes. It offers access to a json attribute class, which reflects the data model JSON attributes. Also, some basic shared functionality is provided by this base class.
Source code in src/cript/nodes/core.py
42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 |
|
json
property
¶
Property to obtain a simple json string.
Calls get_json
with default arguments.
__str__()
¶
Return a string representation of a node data model attributes.
Returns:
Type | Description |
---|---|
str
|
A string representation of the node. |
find_children(search_attr, search_depth=-1, handled_nodes=None)
¶
Finds all the children in a given tree of nodes (specified by its root), that match the criteria of search_attr. If a node is present multiple times in the graph, it is only once in the search results.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
search_attr |
dict
|
What you are searching for within the JSON. Dictionary that specifies which JSON attributes have to be present in a given node. If an attribute is a list, it is sufficient if the specified attributes are in the list, if others are present too, that does not exclude the child. |
required |
search_depth |
int
|
Max depth of the search into the tree. Helpful if circles are expected. -1 specifies no limit |
-1
|
handled_nodes |
Optional[List]
|
A list used to track nodes that have already been processed during the search.
This parameter is primarily used internally to prevent infinite loops in cases
where the node graph contains cycles. When a node is processed, it is added to this list.
If a node is encountered that is already in this list, it is skipped to avoid redundant processing.
By default, this parameter is |
None
|
Returns:
Type | Description |
---|---|
List
|
list of all nodes that match the criteria found within the graph |
Examples:
>>> import cript
>>> # ============= Create nodes =============
>>> my_project = cript.Project(name=f"my_Project")
>>> my_collection = cript.Collection(name="my collection")
>>> my_material_1 = cript.Material(
... name="my material 1", bigsmiles = "my material 1 bigsmiles"
... )
>>> my_material_2 = cript.Material(
... name="my material 2", bigsmiles = "my material 2 bigsmiles"
... )
>>> my_inventory = cript.Inventory(
... name="my inventory", material=[my_material_1, my_material_2]
... )
>>> # ============= Assemble nodes =============
>>> my_project.collection = [my_collection]
>>> my_project.collection[0].inventory = [my_inventory]
>>> # ============= Get list of all material nodes in project =============
>>> all_materials_in_project: list = my_project.find_children({"node": ["Material"]})
Notes
The find_children
method is versatile and can be used to search for nodes based on various criteria.
Here are some examples to illustrate its usage:
- Searching for Specific Node Types:
search_attr = {"node": ["Parameter"]}
will find all nodes of type "Parameter". - Searching with Additional Attributes:
search_attr = {"node": ["Algorithm"], "parameter": {"name" : "update_frequency"}}
will locate "Algorithm" nodes containing a parameter named "update_frequency". Note: For list attributes, a match occurs if the specified attribute is part of the list.- Alternate notation:
{"node": ["Algorithm"], "parameter": [{"name" : "update_frequency"}]}
. In this case, nodes with additional parameters are also included.
- Alternate notation:
- Combining Multiple Search Criteria: This finds all "Algorithm" nodes with both "update_frequency" and "cutoff_distance" parameters.
The search_depth
parameter controls how deep the search goes into the node tree.
A value of -1
indicates no depth limit.
The method effectively handles cycles in the graph by ensuring each node is processed only once.
This makes the function suitable for complex node structures.
Source code in src/cript/nodes/core.py
487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 |
|
get_expanded_json(**kwargs)
¶
Generates a long-form JSON representation of the current node and its hierarchy.
The long-form JSON includes complete details of the node, eliminating the need for references to UUIDs to nodes stored in the CRIPT database. This comprehensive representation is useful for offline storage of CRIPT nodes, transferring nodes between different CRIPT instances, or for backup purposes.
The generated long-form JSON can be reloaded into the SDK using
cript.load_nodes_from_json()
,
ensuring consistency and completeness of the node data.
However, it's important to note that this long-form JSON might not comply directly with the JSON schema
required for POST or PATCH requests to the CRIPT API.
Optional keyword arguments (kwargs
) are supported and are passed directly to json.dumps()
.
These arguments allow customization of the JSON output, such as formatting for readability
or pretty printing.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
**kwargs |
dict
|
Additional keyword arguments for |
{}
|
Returns:
Type | Description |
---|---|
str
|
A comprehensive JSON string representing the current node and its entire hierarchy in long-form. |
Notes
The get_expanded_json()
method differs from the standard json
property or method, which might provide a more condensed version of the node's data.
For more information on condensed JSON and deserialization, please feel free to reference our discussion on deserializing Python nodes to JSON
Examples:
>>> import cript
>>> # ============= Create all needed nodes =============
>>> my_project = cript.Project(name=f"my_Project")
>>> my_collection = cript.Collection(name="my collection")
>>> my_material_1 = cript.Material(
... name="my material 1", bigsmiles = "my material 1 bigsmiles"
... )
>>> my_material_2 = cript.Material(
... name="my material 2", bigsmiles = "my material 2 bigsmiles"
... )
>>> my_inventory = cript.Inventory(
... name="my inventory", material=[my_material_1, my_material_2]
... )
>>> # ============= Assemble nodes =============
>>> my_project.collection = [my_collection]
>>> my_project.collection[0].inventory = [my_inventory]
>>> # ============= Get long form JSON =============
>>> long_form_json = my_project.get_expanded_json(indent=4)
Condensed JSON VS Expanded JSON
Default Condensed JSON¶
This is the JSON when
my_project.json
is called
Expanded JSON¶
This is what is created when
my_project.get_expanded_json()
Source code in src/cript/nodes/core.py
254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 |
|
get_json(handled_ids=None, known_uuid=None, suppress_attributes=None, is_patch=False, condense_to_uuid={'Material': {'parent_material', 'component'}, 'Experiment': {'data'}, 'Inventory': {'material'}, 'Ingredient': {'material'}, 'Property': {'component'}, 'ComputationProcess': {'material'}, 'Data': {'material'}, 'Process': {'product', 'waste'}, 'Project': {'member', 'admin'}, 'Collection': {'member', 'admin'}}, **kwargs)
¶
User facing access to get the JSON of a node.
Opposed to the also available property json this functions allows further control.
Additionally, this function does not call self.validate()
but the property json
does.
We also accept kwargs
, that are passed on to the JSON decoding via json.dumps()
this can be used for example to prettify the output.
Returns named tuple with json and handled ids as result.
Source code in src/cript/nodes/core.py
remove_child(child)
¶
This safely removes the first found child node from the parent.
This requires exact node as we test with is
instead of ==
.
returns True if child was found and deleted, False if child not found, raise DB schema exception if deletion violates DB schema.
Source code in src/cript/nodes/core.py
validate(api=None, is_patch=False, force_validation=False)
¶
Validate this node (and all its children) against the schema provided by the data bank.
Raises:
Exception with more error information.