Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🎉 Adds Drift Detection Demo #690

Merged
merged 8 commits into from
Nov 23, 2023
Merged

🎉 Adds Drift Detection Demo #690

merged 8 commits into from
Nov 23, 2023

Conversation

AlexandreSajus
Copy link
Contributor

Adds a demo about showcasing the ability to select inputs and execute and visualize outputs of data pipelines in a Taipy application using the example of detecting drift on a dataset.

image

(the live demo will have issues until the following issue is fixed: Avaiga/taipy#350)

@AlexandreSajus AlexandreSajus added the 📄 Documentation Internal or public documentation label Oct 25, 2023
@AlexandreSajus AlexandreSajus self-assigned this Oct 25, 2023
Copy link
Member

@jrobinAV jrobinAV left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. This is minor, but I believe we can improve the UX by displaying the scenario viewer and the dag right below the input data nodes selections.

  2. The scenario viewer does not need to be expanded nor expandable.

  3. You did not created a more realistic use case with monthly scenarios with cumulative drift month after month as discussed. I am more than fine with that to make the demo easily understandable. However, Please consider having an advanced version of this demo to first exhibit the cycle usage and second to show how Taipy helps end users managing data overtime. It is part of our will to position Taipy as a tool to help data management operations in production and industrial context.

docs/knowledge_base/demos/drift_detection.md Outdated Show resolved Hide resolved
docs/knowledge_base/demos/drift_detection.md Outdated Show resolved Hide resolved
docs/knowledge_base/demos/drift_detection.md Outdated Show resolved Hide resolved
docs/knowledge_base/demos/drift_detection.md Outdated Show resolved Hide resolved
docs/knowledge_base/demos/drift_detection.md Outdated Show resolved Hide resolved
docs/knowledge_base/demos/drift_detection.md Outdated Show resolved Hide resolved
docs/knowledge_base/demos/index.md Outdated Show resolved Hide resolved
docs/knowledge_base/index.md Outdated Show resolved Hide resolved
docs/knowledge_base/index.md Outdated Show resolved Hide resolved
docs/knowledge_base/demos/index.md Outdated Show resolved Hide resolved
@AlexandreSajus
Copy link
Contributor Author

  1. This is minor, but I believe we can improve the UX by displaying the scenario viewer and the dag right below the input data nodes selections.
  2. The scenario viewer does not need to be expanded nor expandable.
  3. You did not created a more realistic use case with monthly scenarios with cumulative drift month after month as discussed. I am more than fine with that to make the demo easily understandable. However, Please consider having an advanced version of this demo to first exhibit the cycle usage and second to show how Taipy helps end users managing data overtime. It is part of our will to position Taipy as a tool to help data management operations in production and industrial context.
  1. I feel that displaying data and data distribution after selecting the data source makes more sens as you can see the changes without scrolling
  2. Fixed now
  3. Sure, I did not see how to fit this in this demo without making it too complex. I will work on another demo about cycle and data management

@jrobinAV
Copy link
Member

  1. I feel that displaying data and data distribution after selecting the data source makes more sens as you can see the changes without scrolling
  2. Fixed now
  3. Sure, I did not see how to fit this in this demo without making it too complex. I will work on another demo about cycle and data management

Sounds good!

@jrobinAV
Copy link
Member

Any update on this one?

@AlexandreSajus
Copy link
Contributor Author

Any update on this one?

Yeah I fixed what you asked, just waiting for approval

@jrobinAV jrobinAV merged commit d8afca5 into develop Nov 23, 2023
@jrobinAV jrobinAV deleted the demo-drift-detection branch November 23, 2023 15:13
FlorianJacta pushed a commit that referenced this pull request Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📄 Documentation Internal or public documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BUG-Data Node Viewer does not update on scenario execution
2 participants