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

About the size of the input test data #3

Open
azyslzp opened this issue Sep 17, 2020 · 1 comment
Open

About the size of the input test data #3

azyslzp opened this issue Sep 17, 2020 · 1 comment

Comments

@azyslzp
Copy link

azyslzp commented Sep 17, 2020

Hi, Thanks a lot for your sharing! The code have trained and tested in my Server, and there still has a question as,
due to the input size of the vtcnn and mrresnet is fixed to adapt the training data, then if I want to test by using the signal data generated or collected by us, which the length is not the same as the trainning data, how should we do?
cut or sample it?
Thanks a lot~

@isaaccorley
Copy link
Owner

isaaccorley commented Sep 17, 2020

@azyslzp The dataset used for training is the RML2016.10b dataset used in DeepSig's paper Convolutional Radio Modulation Recognition Networks. In the paper it states that each window is composed of 128 microsecond samples implying a 1 MHz sampling frequency and contains between 8-16 symbols. Intuitively, I would think resampling to this frequency while keeping enough symbols in the window based on your test set's baud rate would be appropriate. A side note: the MRResNet model utilizes a Global Average Pooling before the linear layers which means the model isn't constrained to a fixed size input, however you will likely see a performance dip depending on how different your test data is to the training set. Hope this helps.

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

No branches or pull requests

2 participants