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

[ENH] Added test parameters for the LSTM FCNN network #6281

Merged
merged 9 commits into from Apr 14, 2024

Conversation

shlok191
Copy link
Contributor

@shlok191 shlok191 commented Apr 9, 2024

PR Contributes to #3429

Added 2 test parameters for the LSTMFCNNNetwork as mentioned here: #3429. One of the parameters sets out a simpler version of the model, and the other tests a more sophisticated model

What does this implement/fix? Explain your changes.

I have added 2 test parameters for the LSTM-FCNN network returned via the get_test_params function. The test parameters aim to explore 2 quite different variations of the model in the hope to capture a broad spectrum of the model's parameters.

Does your contribution introduce a new dependency? If yes, which one?

It does not!

What should a reviewer concentrate their feedback on?

I would direct anyone's attention to the added function: sktime/networks/lstmfcn.py/get_test_params starting from line 128. I can absolutely work on improving the parameters if they are not quite as good, but that is the only major place I have made a change!

Did you add any tests for the change?

I have not added any tests for the commits I made

PR checklist

For all contributions
  • I've added myself to the list of contributors with any new badges I've earned :-)
    How to: add yourself to the all-contributors file in the sktime root directory (not the CONTRIBUTORS.md). Common badges: code - fixing a bug, or adding code logic. doc - writing or improving documentation or docstrings. bug - reporting or diagnosing a bug (get this plus code if you also fixed the bug in the PR).maintenance - CI, test framework, release.
    See here for full badge reference

  • The PR title starts with either [ENH], [MNT], [DOC], or [BUG]. [BUG] - bugfix, [MNT] - CI, test framework, [ENH] - adding or improving code, [DOC] - writing or improving documentation or docstrings.

@fkiraly fkiraly added module:classification classification module: time series classification module:regression regression module: time series regression enhancement Adding new functionality labels Apr 10, 2024
@fkiraly
Copy link
Collaborator

fkiraly commented Apr 10, 2024

Thanks!

For the tests to run, kindly ensure you adhere to sktime code formatting standards:
https://www.sktime.net/en/stable/developer_guide/coding_standards.html

@shlok191
Copy link
Contributor Author

Oh I see! Thank you so much for the help @fkiraly. I have set up pre-commit now and verified that my code meets the standards before pushing the final fix commit. Hopefully this one works! 😃

Copy link
Collaborator

@fkiraly fkiraly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Can you make sure to:

  • include an empty parameter set - i.e., empty dict?
  • don't set random_state?

@shlok191
Copy link
Contributor Author

Got it, just pushed a commit with the desired changes!

@fkiraly fkiraly merged commit 0185d5c into sktime:main Apr 14, 2024
54 checks passed
toandaominh1997 pushed a commit to toandaominh1997/sktime that referenced this pull request Apr 18, 2024
I have added 2 test parameters for the LSTM-FCNN network returned via
the `get_test_params` function. The test parameters aim to explore 2
quite different variations of the model in the hope to capture a broad
spectrum of the model's parameters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Adding new functionality module:classification classification module: time series classification module:regression regression module: time series regression
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants