guidepost 0.2.12__tar.gz → 0.2.13__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- {guidepost-0.2.12/guidepost.egg-info → guidepost-0.2.13}/PKG-INFO +2 -2
- {guidepost-0.2.12 → guidepost-0.2.13}/README.md +1 -1
- guidepost-0.2.13/guidepost/version.py +2 -0
- {guidepost-0.2.12 → guidepost-0.2.13/guidepost.egg-info}/PKG-INFO +2 -2
- guidepost-0.2.12/guidepost/version.py +0 -2
- {guidepost-0.2.12 → guidepost-0.2.13}/LICENSE +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/figs/__init__.py +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/figs/guidepost_tutorial_info.png +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/guidepost/__init__.py +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/guidepost/guidepost.js +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/guidepost/guidepost.py +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/guidepost.egg-info/SOURCES.txt +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/guidepost.egg-info/dependency_links.txt +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/guidepost.egg-info/requires.txt +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/guidepost.egg-info/top_level.txt +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/pyproject.toml +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/setup.cfg +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/setup.py +0 -0
- {guidepost-0.2.12 → guidepost-0.2.13}/tutorials/__init__.py +0 -0
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.2
|
|
2
2
|
Name: guidepost
|
|
3
|
-
Version: 0.2.
|
|
3
|
+
Version: 0.2.13
|
|
4
4
|
Summary: Guidepost. An overview visualization for understanding supercomputer queue data.
|
|
5
5
|
Home-page: https://github.com/cscully-allison/guidepost
|
|
6
6
|
Author: Connor Scully-Allison
|
|
@@ -79,7 +79,7 @@ Here is a sample table containg jobs-related data from a supercomputer schedulin
|
|
|
79
79
|
| 12345 | 2023-11-01 21:19:33 |5.2 | 10 | short | Complete | User1 |
|
|
80
80
|
| 12346 | 2023-11-01 21:20:01 |12.0 | 20 | long | Running | User2 |
|
|
81
81
|
|
|
82
|
-
In this example, the three data values we will use for our x, y and color variables are: start_time, queue_wait and nodes_requested. We would also like to use `parition` to facet our data and `user` as an additional categorical variable to filter on. In the [next section](#3-configure-visualization), we show how to specify which columns in your dataset correspond to parts of the
|
|
82
|
+
In this example, the three data values we will use for our x, y and color variables are: start_time, queue_wait and nodes_requested. We would also like to use `parition` to facet our data and `user` as an additional categorical variable to filter on. In the [next section](#3-configure-visualization), we show how to specify which columns in your dataset correspond to parts of the visualization.
|
|
83
83
|
|
|
84
84
|
The `load_data()` function will format your data for json serialization and will update the visualization if it has already been run. This function will report out any columns or rows which are dropped from the original dataset due to conainting `null`/`NaN`/`None` values or unallowed datatypes like `timedelta`s.
|
|
85
85
|
|
|
@@ -51,7 +51,7 @@ Here is a sample table containg jobs-related data from a supercomputer schedulin
|
|
|
51
51
|
| 12345 | 2023-11-01 21:19:33 |5.2 | 10 | short | Complete | User1 |
|
|
52
52
|
| 12346 | 2023-11-01 21:20:01 |12.0 | 20 | long | Running | User2 |
|
|
53
53
|
|
|
54
|
-
In this example, the three data values we will use for our x, y and color variables are: start_time, queue_wait and nodes_requested. We would also like to use `parition` to facet our data and `user` as an additional categorical variable to filter on. In the [next section](#3-configure-visualization), we show how to specify which columns in your dataset correspond to parts of the
|
|
54
|
+
In this example, the three data values we will use for our x, y and color variables are: start_time, queue_wait and nodes_requested. We would also like to use `parition` to facet our data and `user` as an additional categorical variable to filter on. In the [next section](#3-configure-visualization), we show how to specify which columns in your dataset correspond to parts of the visualization.
|
|
55
55
|
|
|
56
56
|
The `load_data()` function will format your data for json serialization and will update the visualization if it has already been run. This function will report out any columns or rows which are dropped from the original dataset due to conainting `null`/`NaN`/`None` values or unallowed datatypes like `timedelta`s.
|
|
57
57
|
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
Metadata-Version: 2.2
|
|
2
2
|
Name: guidepost
|
|
3
|
-
Version: 0.2.
|
|
3
|
+
Version: 0.2.13
|
|
4
4
|
Summary: Guidepost. An overview visualization for understanding supercomputer queue data.
|
|
5
5
|
Home-page: https://github.com/cscully-allison/guidepost
|
|
6
6
|
Author: Connor Scully-Allison
|
|
@@ -79,7 +79,7 @@ Here is a sample table containg jobs-related data from a supercomputer schedulin
|
|
|
79
79
|
| 12345 | 2023-11-01 21:19:33 |5.2 | 10 | short | Complete | User1 |
|
|
80
80
|
| 12346 | 2023-11-01 21:20:01 |12.0 | 20 | long | Running | User2 |
|
|
81
81
|
|
|
82
|
-
In this example, the three data values we will use for our x, y and color variables are: start_time, queue_wait and nodes_requested. We would also like to use `parition` to facet our data and `user` as an additional categorical variable to filter on. In the [next section](#3-configure-visualization), we show how to specify which columns in your dataset correspond to parts of the
|
|
82
|
+
In this example, the three data values we will use for our x, y and color variables are: start_time, queue_wait and nodes_requested. We would also like to use `parition` to facet our data and `user` as an additional categorical variable to filter on. In the [next section](#3-configure-visualization), we show how to specify which columns in your dataset correspond to parts of the visualization.
|
|
83
83
|
|
|
84
84
|
The `load_data()` function will format your data for json serialization and will update the visualization if it has already been run. This function will report out any columns or rows which are dropped from the original dataset due to conainting `null`/`NaN`/`None` values or unallowed datatypes like `timedelta`s.
|
|
85
85
|
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|