executor
Base classes and functions for handling Task
execution.
Executors run a Task
as a subprocess and handle all communication with other
services, e.g., the eLog. They accept specific handlers to override default
stream parsing.
Event handlers/hooks are implemented as standalone functions which can be added to an Executor.
Classes:
Name | Description |
---|---|
BaseExecutor |
Abstract base class from which all Executors are derived. |
Executor |
Default Executor implementing all basic functionality and IPC. |
MPIExecutor |
Runs exactly as the Executor but submits the Task using MPI. |
Exceptions
BaseExecutor
Bases: ABC
ABC to manage Task execution and communication with user services.
When running in a workflow, "tasks" (not the class instances) are submitted
as Executors
. The Executor manages environment setup, the actual Task
submission, and communication regarding Task results and status with third
party services like the eLog.
Attributes:
Methods:
Name | Description |
---|---|
add_hook |
str, hook: Callable[[None], None]) -> None: Create a new hook to be called each time a specific event occurs. |
add_default_hooks |
Populate the event hooks with the default functions. |
update_environment |
Dict[str, str], update_path: str): Update the environment that is passed to the Task subprocess. |
execute_task |
Run the task as a subprocess. |
Source code in lute/execution/executor.py
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 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 |
|
Hooks
A container class for the Executor's event hooks.
There is a corresponding function (hook) for each event/signal. Each function takes two parameters - a reference to the Executor (self) and a reference to the Message (msg) which includes the corresponding signal.
Source code in lute/execution/executor.py
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 |
|
__init__(task_name, communicators, poll_interval=0.05)
The Executor will manage the subprocess in which task_name
is run.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
task_name
|
str
|
The name of the Task to be submitted. Must match the Task's class name exactly. The parameter specification must also be in a properly named model to be identified. |
required |
communicators
|
List[Communicator]
|
A list of one or more communicators which manage information flow to/from the Task. Subclasses may have different defaults, and new functionality can be introduced by composing Executors with communicators. |
required |
poll_interval
|
float
|
Time to wait between reading/writing to the managed subprocess. In seconds. |
0.05
|
Source code in lute/execution/executor.py
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 |
|
_continue(proc)
Resume a stopped Task subprocess.
Source code in lute/execution/executor.py
600 601 602 603 |
|
_finalize_task(proc)
abstractmethod
Any actions to be performed after the Task has ended.
Examples include a final clearing of the pipes, retrieving results, reporting to third party services, etc.
Source code in lute/execution/executor.py
476 477 478 479 480 481 482 483 |
|
_pre_task()
Any actions to be performed before task submission.
This method may or may not be used by subclasses. It may be useful for logging etc.
Source code in lute/execution/executor.py
437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 |
|
_run_tasklets(*, when)
Run all tasklets of the specified kind.
Source code in lute/execution/executor.py
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 |
|
_set_result_from_parameters()
Use TaskParameters object to set TaskResult fields.
A result may be defined in terms of specific parameters. This is most
useful for ThirdPartyTasks which would not otherwise have an easy way of
reporting what the TaskResult is. There are two options for specifying
results from parameters:
1. A single parameter (Field) of the model has an attribute
is_result
. This is a bool indicating that this parameter points
to a result. E.g. a parameter output
may set is_result=True
.
2. The TaskParameters.Config
has a result_from_params
attribute.
This is an appropriate option if the result is determinable for
the Task, but it is not easily defined by a single parameter. The
TaskParameters.Config.result_from_param can be set by a custom
validator, e.g. to combine the values of multiple parameters into
a single result. E.g. an out_dir
and out_file
parameter used
together specify the result. Currently only string specifiers are
supported.
A TaskParameters object specifies that it contains information about the result by setting a single config option: TaskParameters.Config.set_result=True In general, this method should only be called when the above condition is met, however, there are minimal checks in it as well.
Source code in lute/execution/executor.py
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 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 |
|
_shell_source()
Actually shell source step.
This is run prior to Task execution.
Source code in lute/execution/executor.py
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 |
|
_stop(proc)
Stop the Task subprocess.
Source code in lute/execution/executor.py
595 596 597 598 |
|
_store_configuration()
Store configuration and results in the LUTE database.
Source code in lute/execution/executor.py
573 574 575 |
|
_sub_tasklet_parameters(args)
Substitute tasklet arguments using TaskParameters members.
Source code in lute/execution/executor.py
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 |
|
_submit_cmd(executable_path, params)
Return a formatted command for launching Task subprocess.
May be overridden by subclasses.
The default submission uses the Executor environment. This ensures that all necessary packages (e.g. Pydantic for validation) are available to the startup scripts. If a Task has a different environment it will be swapped prior to execution.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
executable_path
|
str
|
Path to the LUTE subprocess script. |
required |
params
|
str
|
String of formatted command-line arguments. |
required |
Returns:
Name | Type | Description |
---|---|---|
cmd |
str
|
Appropriately formatted command for this Executor. |
Source code in lute/execution/executor.py
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 |
|
_task_is_running(proc)
Whether a subprocess is running.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
proc
|
Popen
|
The subprocess to determine the run status of. |
required |
Returns:
Name | Type | Description |
---|---|---|
bool |
bool
|
Is the subprocess task running. |
Source code in lute/execution/executor.py
577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 |
|
_task_loop(proc)
abstractmethod
Actions to perform while the Task is running.
This function is run in the body of a loop until the Task signals that its finished.
Source code in lute/execution/executor.py
467 468 469 470 471 472 473 474 |
|
add_default_hooks()
abstractmethod
Populate the set of default event hooks.
Source code in lute/execution/executor.py
340 341 342 343 344 |
|
add_hook(event, hook)
Add a new hook.
Each hook is a function called any time the Executor receives a signal for a particular event, e.g. Task starts, Task ends, etc. Calling this method will remove any hook that currently exists for the event. I.e. only one hook can be called per event at a time. Creating hooks for events which do not exist is not allowed.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
event
|
str
|
The event for which the hook will be called. |
required |
Source code in lute/execution/executor.py
318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 |
|
add_tasklet(tasklet, args, when='after', set_result=False, set_summary=False)
Add/register a tasklet to be run by the Executor.
Adds a tasklet to be run by the Executor in addition to the main Task. The tasklet can be run before or after the main Task has been run.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
tasklet
|
Callable[[Any], Any]
|
The tasklet (function) to run. |
required |
args
|
List[Any]
|
A list of all the arguments to be passed to the
tasklet. Arguments can include substitutions for parameters to
be extracted from the TaskParameters object. The same jinja-like
syntax used in configuration file substiutions is used to specify
a parameter substitution in an argument. E.g. if a Task to be
run has a parameter |
required |
when
|
str
|
When to run the tasklet. Either |
'after'
|
set_result
|
bool
|
Whether to use the output from the tasklet as the result of the main Task. Default is False. |
False
|
set_summary
|
bool
|
Whether to use the output from the tasklet as the summary of the main Task. Default is False. |
False
|
Source code in lute/execution/executor.py
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 |
|
execute_task()
Run the requested Task as a subprocess.
Source code in lute/execution/executor.py
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 |
|
process_results()
Perform any necessary steps to process TaskResults object.
Processing will depend on subclass. Examples of steps include, moving files, converting file formats, compiling plots/figures into an HTML file, etc.
Source code in lute/execution/executor.py
725 726 727 728 729 730 731 732 |
|
shell_source(env)
Source a script.
Unlike update_environment
this method sources a new file.
We prepend a token to each environment variable. This allows the initial part of the Task to be run using the appropriate environment.
The environment variables containing the token will be swapped in using their appropriate form prior to the actual execution of Task code.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
env
|
str
|
Path to the script to source. |
required |
Source code in lute/execution/executor.py
390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 |
|
update_environment(env, update_path='prepend')
Update the stored set of environment variables.
These are passed to the subprocess to setup its environment.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
env
|
Dict[str, str]
|
A dictionary of "VAR":"VALUE" pairs of environment variables to be added to the subprocess environment. If any variables already exist, the new variables will overwrite them (except PATH, see below). |
required |
update_path
|
str
|
If PATH is present in the new set of variables, this argument determines how the old PATH is dealt with. There are three options: * "prepend" : The new PATH values are prepended to the old ones. * "append" : The new PATH values are appended to the old ones. * "overwrite" : The old PATH is overwritten by the new one. "prepend" is the default option. If PATH is not present in the current environment, the new PATH is used without modification. |
'prepend'
|
Source code in lute/execution/executor.py
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 |
|
Executor
Bases: BaseExecutor
Basic implementation of an Executor which manages simple IPC with Task.
Attributes:
Methods:
Name | Description |
---|---|
add_hook |
str, hook: Callable[[None], None]) -> None: Create a new hook to be called each time a specific event occurs. |
add_default_hooks |
Populate the event hooks with the default functions. |
update_environment |
Dict[str, str], update_path: str): Update the environment that is passed to the Task subprocess. |
execute_task |
Run the task as a subprocess. |
Source code in lute/execution/executor.py
738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 |
|
_finalize_task(proc)
Any actions to be performed after the Task has ended.
Examples include a final clearing of the pipes, retrieving results, reporting to third party services, etc.
Source code in lute/execution/executor.py
912 913 914 915 916 917 918 |
|
_process_elog_plot(plots)
Process an ElogSummaryPlots
Writes out the eLog summary plot for display and returns the path of where the plots were written out so they can be stored as the result payload.
ElogSummaryPlots objects already convert the plots to a byte stream which can be directly written to an HTML file.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
plots
|
ElogSummaryPlots
|
The plots dataclass. |
required |
Returns:
Name | Type | Description |
---|---|---|
path |
str
|
Path the plots were written out to. |
Source code in lute/execution/executor.py
954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 |
|
_process_result_summary(summary)
Process an object destined for the results summary.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
summary
|
Any
|
The object to be set as a summary. If a dictionary it is assumed to be a set of key/value pairs to be written out as run parameters in the eLog. If a list each item is processed individually. |
required |
Source code in lute/execution/executor.py
987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 |
|
_process_results()
Performs result processing.
Actions include:
- For ElogSummaryPlots
, will save the summary plot to the appropriate
directory for display in the eLog.
Source code in lute/execution/executor.py
920 921 922 923 924 925 926 927 928 929 |
|
_process_summary_run_params(params)
Process a dictionary of run parameters to be posted to the eLog.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
params
|
Dict[str, str]
|
Key/value pairs to be posted as run parameters. |
required |
Returns:
Name | Type | Description |
---|---|---|
summary_str |
str
|
New string of key/value pairs to be stored in summary field of the database. |
Source code in lute/execution/executor.py
1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 |
|
_task_loop(proc)
Actions to perform while the Task is running.
This function is run in the body of a loop until the Task signals that its finished.
Source code in lute/execution/executor.py
885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 |
|
add_default_hooks()
Populate the set of default event hooks.
Source code in lute/execution/executor.py
772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 |
|
MPIExecutor
Bases: Executor
Runs first-party Tasks that require MPI.
This Executor is otherwise identical to the standard Executor, except it
uses mpirun
for Task
submission. Currently this Executor assumes a job
has been submitted using SLURM as a first step. It will determine the number
of MPI ranks based on the resources requested. As a fallback, it will try
to determine the number of local cores available for cases where a job has
not been submitted via SLURM. On S3DF, the second determination mechanism
should accurately match the environment variable provided by SLURM indicating
resources allocated.
This Executor will submit the Task to run with a number of processes equal to the total number of cores available minus 1. A single core is reserved for the Executor itself. Note that currently this means that you must submit on 3 cores or more, since MPI requires a minimum of 2 ranks, and the number of ranks is determined from the cores dedicated to Task execution.
Methods:
Name | Description |
---|---|
_submit_cmd |
Run the task as a subprocess using |
Source code in lute/execution/executor.py
1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 |
|
_submit_cmd(executable_path, params)
Override submission command to use mpirun
Parameters:
Name | Type | Description | Default |
---|---|---|---|
executable_path
|
str
|
Path to the LUTE subprocess script. |
required |
params
|
str
|
String of formatted command-line arguments. |
required |
Returns:
Name | Type | Description |
---|---|---|
cmd |
str
|
Appropriately formatted command for this Executor. |
Source code in lute/execution/executor.py
1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 |
|