You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the FeatureBuilder (feature_builder.py) assumes that we are passing in an output file path that contains either "chat" or "turn" in the name, as it saves the featurized content into either a "chat" folder or "turn" folder based on user
specifications.
We should think carefully about this design decision. Can we make the FeatureBuilder robust to output paths that do not have this in the path name? Or, if we absolutely require the output path to have the right keywords in it, can we add error checking and documentation so that when we fail, we fail noisily?
The text was updated successfully, but these errors were encountered:
Currently, the FeatureBuilder (
feature_builder.py
) assumes that we are passing in an output file path that contains either "chat" or "turn" in the name, as it saves the featurized content into either a "chat" folder or "turn" folder based on userspecifications.
Relevant code:
We should think carefully about this design decision. Can we make the FeatureBuilder robust to output paths that do not have this in the path name? Or, if we absolutely require the output path to have the right keywords in it, can we add error checking and documentation so that when we fail, we fail noisily?
The text was updated successfully, but these errors were encountered: