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
I am trying to use the nilmtk library in aws with the sagemaker service, to do this I start with the basics, which is simply to use the redd converter with the csv data that I uploaded to s3 to a stipulated path.
As inputs, the convert_redd function asks for an input path where the files are and an output path. As input I give the s3 uri path where I have the csv files.
Within the entry route are the files of each of the houses at a low frequency.
When I run the above script, I get an os error, and it's as if the specified path is set to the path where the jupyter sagemaker session is located.
When running it locally, with routes from my pc it works fine for me, the problem is when I use aws sagemaker and s3, does anyone know what mistake I am making or how it can be solved.
The stupid solution that I will apply is to upload the h5 that I already ran locally to aws, but it should not be like that.
The text was updated successfully, but these errors were encountered:
Good evening
I am trying to use the nilmtk library in aws with the sagemaker service, to do this I start with the basics, which is simply to use the redd converter with the csv data that I uploaded to s3 to a stipulated path.
As inputs, the convert_redd function asks for an input path where the files are and an output path. As input I give the s3 uri path where I have the csv files.
Within the entry route are the files of each of the houses at a low frequency.
When I run the above script, I get an os error, and it's as if the specified path is set to the path where the jupyter sagemaker session is located.
When running it locally, with routes from my pc it works fine for me, the problem is when I use aws sagemaker and s3, does anyone know what mistake I am making or how it can be solved.
The stupid solution that I will apply is to upload the h5 that I already ran locally to aws, but it should not be like that.
The text was updated successfully, but these errors were encountered: