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
It is possible to use the same CSV file for both target (labels) and input (latents) file. However, the dataLoader object will duplicate the entries during the join operation. We can default to force join_left when a single input file is provided (or name duplication, it is equivalent)
This might require either:
Provide the CLI option for a single input/target file definition at invocation time
Detect name duplication at runtime and enable the join_left option
We will always assume that the input CSV (latents) contains the relevant metadata fields we want to propagate to the exported dataframe
The text was updated successfully, but these errors were encountered:
It is possible to use the same CSV file for both target (labels) and input (latents) file. However, the dataLoader object will duplicate the entries during the join operation. We can default to force join_left when a single input file is provided (or name duplication, it is equivalent)
This might require either:
We will always assume that the input CSV (latents) contains the relevant metadata fields we want to propagate to the exported dataframe
The text was updated successfully, but these errors were encountered: