I recently created a prototype model in tensorflow, I'm asking if where is the saved model saved in my pc, its file location. saving my file outputted this info:
INFO:tensorflow:Assets written to: m_translator\assets
and I don't know what clearly this is hope there's someone who can explain this to me
From the info you have given, it says that the files are written to m_translator. Once check in your PC in the same directory where you are running your code if there is any folder named m_translator or check in the filepath you have provided while saving the model. Thank You.
Related
i prepared my dataset and created a version of it. Then i tried to export dataset in TensorFlow Object Detection CSV format but when i got output of given zip file. But i see that there is nothing inside the zip file except "README.roboflow.txt" and "README.Dataset.txt"
Is there anything i'm doing wrong or it's in process of development ? or it's a bug?
Thanks
I just tried this and was able to get my test, train, valid in the folder which also included the README.Dataset.txt and README.roboflow.txt.
Can you try again or share the email you used to build this project so one of us Roboflow staff members can take a look at it? You can feel free to dm it to me in our forum if it still doesn't work.
Kelly M., Developer Advocate
I have been reading and working on SO questions related to the Street View House Numbers (SVHN) datasets. The files are available at 2 different locations:
Stanford:
The Street View House Numbers (SVHN) Dataset
kaggle:
Street View House Numbers (SVHN) | Kaggle
My question is related to the format of the digitStruct.mat files for each image set (train, test, and extras). These define the name, label, and bounding box dimensions for each image. As I understand, the mat file is written as a Matlab structure in HDF5 format (that can be read with h5py).
I have been able to access and read the digitStruct.mat files from kaggle with h5py. I cannot open the same files from the Stanford site with h5py (or with HDFView). Some SO posts I've read indicate the Stanford files are an older Matlab format and should be read with scipy.io.loadmat.
Are the files at Stanford and kaggle the same?
If not, what are the differences?
Should I be able to open the Stanford digitStruct.mat files with h5py?
If so, what method should I use to download and extract the Standford tar.gz files? (FYI, I'm on Win-7, and have been using HTTP download and WinZip to extract.)
I am adding additional info to document different behavior observed with different .mat files. It may help with diagnosis.
I can open and operate on .mat files from kaggle with this call:
h5f = h5py.File('digitStruct.mat','r')
For files from Stanford, I get different errors depending on the file and function used to open.
The command below executes without an error message. That leads me to believe it is not a Matlab v7.3 file that can be opened with h5py.
mat = scipy.io.loadmat('./Stanford/test_32x32.mat')
Both of these calls do not work (brief error message provided):
mat = scipy.io.loadmat('./test/digitStruct.mat')
Traceback...
NotImplementedError: Please use HDF reader for matlab v7.3 files
h5f = h5py.File('./test/digitStruct.mat','r')
Traceback...
OSError: Unable to open file (file signature not found)
In addition, I cannot open test/digitStruct.mat with HDFView. My conclusion for the Stanford digitStruct.mat files: they might be Matlab v7.3 files, but were corrupted when I downloaded. However, I'm not sure what I did wrong (since I can download and read kaggle files without problems).
With some Linux detective work, I figured out the problem.
As I suspected, the digitStruct.mat files extracted from the *.tar.gz files on the Stanford site are HDF5 (Matlab v7.3) files, and were corrupted when I downloaded.
To confirm, I downloaded the 3 tar.gz files with a browser on a Linux system, then used the tar command to extract them, and successfully opened with h5py on Linux. I then transferred them to my Windows system, and each worked as expected with h5py.
This is a little surprising, as I have used WinZip to extract tarball files in the past. Apparently there's something special about these that caused the corruption.
Hopefully this saves someone the same headache in the future.
Note: the 3 xxxx_32x32.mat files are an older Matlab format that must be accessed with scipy.io.loadmat()
I'm using valgrind's callgrind to profile a program and then kcachegrind to view the profile data. I've copied callgrind's output file to a different machine and have a copy of the source code there, but apparently the path information of the source code is baked into callgrind's format. This means kcachegrind is looking in the wrong place:
Is there a way to pass a relative source code path so that I can profile the program on one machine but then transport the profiling data to another machine and still view the source code?
I had originally tried the sed route and that didn't work. But I looked at that solution again and the problem was that paths with '~' don't work with kcachegrind it seems.
I used "inotifywait" to trace the file's operation. I want to know its structure. How does it know that a file is created, read and deleted? How does it know that a directory is created and removed? What are kernel's files that inotifywait tracks. Which kernel's files doing these file's operation? Please help me find out. Thank you.
inotify is a feature built into the kernel (first included in version 2.6.13). Since a file create request or a file close (on write complete) request needs to go through the kernel, it is implicitly aware of all these operations. Same goes for directories, since the kernel is aware if the file created is a directory or not.
Which kernel's files doing these file's operation?
Are you asking for the inotify source code? You could possible start by looking at the header files here: http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/include/linux/ (inotify.h)
I am using Qt5.2-msvc. I wrote a library project. I want to make a copy of the library(just the dll file) while building it to the another directory.
I don't want to use DESTDIR since I just want to copy one single dll.
I have tried QMAKE_PRE_LINK and QMAKE_POST_LINK, but none of them works and gives me error.
Any guidance will be appreciated :)
Thanks a lot.