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

Switching from ACTGAN to NavFT as the default SDK Blueprint #509

Merged
merged 10 commits into from
Feb 3, 2025

Conversation

Marjan-emd
Copy link
Contributor

In this PR , the SDK Gretel 101 Blueprint model is changed from ACTGAN to NavFT.

To show case NavFT capabilities, the sample datasets are changed to:

  • Patient events: a sequential dataset. Model handling time series data, free text and json data types. (total runtime ~25min) => default data
  • Car accident: Model handling high row and column counts (25K and 46 respectively). This dataset also includes various data types including boolean, categorical, numeric and free text. (total runtime ~less than an hour)

Copy link

vercel bot commented Jan 14, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
gretel-blueprints ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 30, 2025 11:29pm

sdk_blueprints/Gretel_101_Blueprint.ipynb Outdated Show resolved Hide resolved
sdk_blueprints/Gretel_101_Blueprint.ipynb Outdated Show resolved Hide resolved
sdk_blueprints/Gretel_101_Blueprint.ipynb Outdated Show resolved Hide resolved
sdk_blueprints/Gretel_101_Blueprint.ipynb Outdated Show resolved Hide resolved
sdk_blueprints/Gretel_101_Blueprint.ipynb Outdated Show resolved Hide resolved
sdk_blueprints/Gretel_101_Blueprint.ipynb Outdated Show resolved Hide resolved
sdk_blueprints/Gretel_101_Blueprint.ipynb Outdated Show resolved Hide resolved
sdk_blueprints/Gretel_101_Blueprint.ipynb Outdated Show resolved Hide resolved
@kboyd
Copy link
Contributor

kboyd commented Jan 29, 2025

@alexahaushalter should there also be a reviewer from front-end for the blueprints repo in general? E.g., do we do 2 separate PRs, one to main and then one to develop for these notebooks?

Marjan-emd and others added 2 commits January 30, 2025 14:28
Co-authored-by: Kendrick Boyd <[email protected]>
@Marjan-emd
Copy link
Contributor Author

@alexahaushalter should there also be a reviewer from front-end for the blueprints repo in general? E.g., do we do 2 separate PRs, one to main and then one to develop for these notebooks?

Correct, There are 2 separate PRs for this update to be affective in dev. @alexahaushalter and I discussed it with Nathen, and he mentioned that he will cherry pick all the commits to main into development via this PR.

@alexahaushalter
Copy link
Contributor

@alexahaushalter should there also be a reviewer from front-end for the blueprints repo in general? E.g., do we do 2 separate PRs, one to main and then one to develop for these notebooks?

Correct, There are 2 separate PRs for this update to be affective in dev. @alexahaushalter and I discussed it with Nathen, and he mentioned that he will cherry pick all the commits to main into development via this PR.

Yes let's follow that approach, thanks! No need to have additional FE review since we have informed Nathan.

@Marjan-emd Marjan-emd merged commit 028caa2 into main Feb 3, 2025
5 checks passed
@Marjan-emd Marjan-emd deleted the me/rds-1262 branch February 4, 2025 00:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants