| Demo-data-exploration |
26 |
average of 4.50 from 1 users |
Florian_Dietz |
This starts Rule a major series of tasks, each dependent on each other.
The purpose of this Rule is the initial exploration of the content of a table.
1. Acquire a file from the user through [[symbol:task_obtain_file_from_user]].
2. Transform the file into a pickled Pandas DataFrame using [[symbol:task_convert_file_type]].
3. Cleanse and analyze the file through [[symbol:task_data_cleansing_and_analysis_for_pandas]].
4. Present the results through [[symbol:task_present_table_for_pandas]].
5. Perform additional, more complex analyses through [[symbol:task_explore_data_for_pandas]]. |
Yes
|
| Demo-data-exploration-skip-analysis |
2 |
- |
Florian_Dietz |
If [[symbol:demo_data_exploration_skip_analysis]] is set, reacts to [[rule:Demo-data-exploration]] by marking [[symbol:task_data_cleansing_and_analysis_for_pandas]] as done as soon as [[program:BasicDataCleansingAndAnalysisForPandas]] has run once. The result of this is that all in-depth analysis is skipped, and the only analysis that is done is the perfunctory assigning of info_ Tags by [[program:BasicDataCleansingAndAnalysisForPandas]] when it runs the first time. |
Yes
|
| Demo-data-exploration-restrict-analysis-in-stages |
12 |
- |
Florian_Dietz |
This Rule works with [[rule:Demo-data-exploration]] and uses [[symbol:restrict_analysis_types_for_data_analysis_pandas]] to restrict the types of analyses that are used in stages. |
Yes
|
| Demo-data-exploration-import-analysis |
3 |
- |
Florian_Dietz |
Reacts to [[rule:Demo-data-exploration]] and offers to import an existing analysis when [[symbol:task_obtain_file_from_user]] starts. |
Yes
|
| Demo-data-exploration-export-analysis |
8 |
- |
Florian_Dietz |
Reacts to [[rule:Demo-data-exploration]] and stores the result of the analysis, for later import. |
Yes
|
| Enrich-convert-csv-to-pandas-dataframe |
3 |
- |
initial_tools |
React to a [[symbol:task_convert_file_type]] with a [[symbol:require_format_excel]].
If the file targeted by the [[symbol:require_format_pickled_pandas_dataframe]] is of type csv, runs [[program:Enrich_Convert_CSV_to_Pandas_Dataframe]] on it.
This Rule does NOT use chaining. It was added after the following Rules, to speed things up a bit because it turned out that the conversion CSV->Pandas needed to be fast and so couldn't take two steps:
-[[rule:Enrich-convert-csv-to-excel-with-possible-chaining]]
-[[rule:Enrich-convert-excel-to-pandas-dataframe-with-possible-chaining]]
-[[rule:Enrich-convert-pandas-dataframe-to-csv-with-possible-chaining]] |
Yes
|
| Enrich-convert-pandas-dataframe-to-csv-with-possible-chaining |
7 |
- |
initial_tools |
React to a [[symbol:task_convert_file_type]] with a [[symbol:require_format_csv]].
If the file targeted by the [[symbol:require_format_csv]] is a pickled Pandas dataframe (file ending .pickle or .pkl), runs [[program:Enrich_Convert_Pandas_Dataframe_to_CSV]] on it.
Otherwise creates a [[symbol:require_format_pickled_pandas_dataframe]] and waits until it is solved. In this way, multiple file conversions can be chained together automatically if necessary.
Note: The three Rules [[rule:Enrich-convert-csv-to-excel-with-possible-chaining]], [[rule:Enrich-convert-excel-to-pandas-dataframe-with-possible-chaining]] and [[rule:Enrich-convert-pandas-dataframe-to-csv-with-possible-chaining]] were designed together and can automatically trigger each other in a circular fashion, so that any of the three datatypes can be converted into any of the other two.
(A note for new developers joining LOD: the ability to chain different conversions together automatically is a fairly advanced feature, which... |
Yes
|
| Enrich-convert-csv-to-excel-with-possible-chaining |
7 |
- |
initial_tools |
React to a [[symbol:task_convert_file_type]] with a [[symbol:require_format_excel]].
If the file targeted by the [[symbol:require_format_excel]] is of type csv, runs [[program:Enrich_Convert_CSV_to_Excel]] on it.
Otherwise creates a [[symbol:require_format_csv]] and waits until it is solved. In this way, multiple file conversions can be chained together automatically if necessary.
Note: The three Rules [[rule:Enrich-convert-csv-to-excel-with-possible-chaining]], [[rule:Enrich-convert-excel-to-pandas-dataframe-with-possible-chaining]] and [[rule:Enrich-convert-pandas-dataframe-to-csv-with-possible-chaining]] were designed together and can automatically trigger each other in a circular fashion, so that any of the three datatypes can be converted into any of the other two.
(A note for new developers joining LOD: the ability to chain different conversions together automatically is a fairly advanced feature, which is why this Rule is probably larger than you would expect. In contrast,... |
Yes
|
| Spawn-recognize-failure-to-convert-file |
7 |
- |
initial_tools |
React to a [[symbol:task_convert_file_type]].
Will display a message to the user admitting failure if it turns out that the task can't be solved. |
Yes
|
| Recognize-task-to-convert-file-to-pickled-pandas-dataframe |
7 |
- |
initial_tools |
This Rule calls [[program:Interact_ask_user_if_they_want_file_conversion]]
When (1) the keyword 'convert' comes up as a [[symbol:user_input_keyword]] and (2) 'pandas' comes up as a [[symbol:?user_input_command_keyword]] and (3) a file is uploaded by the user, THEN runs [[program:Interact_ask_user_if_they_want_file_conversion]].
|
Yes
|
