Skip to content

Feature/data smoothing#72

Open
jwasikpsnc wants to merge 30 commits into
iterorganization:developfrom
jwasikpsnc:feature/data-smoothing
Open

Feature/data smoothing#72
jwasikpsnc wants to merge 30 commits into
iterorganization:developfrom
jwasikpsnc:feature/data-smoothing

Conversation

@jwasikpsnc
Copy link
Copy Markdown
Collaborator

  • Updated /info/data_manipulation_methods/ workflow
  • Added Gaussian and Savitzky-Golay filters
  • Passing whole request structure to data_source layer instead of parameters extraction
  • Added smoothing tests
  • Updated docs

jwasikpsnc and others added 21 commits April 17, 2026 14:04
…re/data-smoothing

# Conflicts:
#	backend/ibex/core/ibex_service.py
#	backend/ibex/data_source/data_source_interface.py
#	backend/ibex/data_source/imas_python_source.py
#	backend/ibex/data_source/imas_python_source_utils.py
#	backend/ibex/endpoints/data.py
#	backend/ibex/endpoints/info.py
#	backend/ibex/endpoints/schemas/info_schemas.py
@read-the-docs-community
Copy link
Copy Markdown

read-the-docs-community Bot commented May 25, 2026

Documentation build overview

📚 imas-ibex | 🛠️ Build #33006458 | 📁 Comparing 9fb50d8 against latest (d786f12)

  🔍 Preview build  

130 files changed · + 80 added · ± 50 modified

+ Added

± Modified

Comment thread backend/ibex/data_source/imas_python_source.py
@jwasikpsnc
Copy link
Copy Markdown
Collaborator Author

@olivhoenen
Do you think it is good idea to create github action to find and report "problematic" unicode characters?
Already found more of them, namely:
u2018 - LEFT SINGLE QUOTATION MARK (‘)
u2019 - RIGHT SINGLE QUOTATION MARK (’)
They came to code when i was copying parameters description from scipy, e.g.:
:param cval: Value to fill past the edges of the input if mode is ‘constant’. Default is 0.0.
imas_python_source_utils.py:28
Fortunately they are located in docstring, but actively hunting for them would save us time for debugging in the future.

@olivhoenen
Copy link
Copy Markdown
Contributor

@olivhoenen Do you think it is good idea to create github action to find and report "problematic" unicode characters? Already found more of them, namely: u2018 - LEFT SINGLE QUOTATION MARK (‘) u2019 - RIGHT SINGLE QUOTATION MARK (’) They came to code when i was copying parameters description from scipy, e.g.: :param cval: Value to fill past the edges of the input if mode is ‘constant’. Default is 0.0. imas_python_source_utils.py:28 Fortunately they are located in docstring, but actively hunting for them would save us time for debugging in the future.

Yes, having the linter checking for these is indeed a good idea @jwasikpsnc

@jwasikpsnc
Copy link
Copy Markdown
Collaborator Author

Ok, will do it in separate branch

Comment thread backend/ibex/endpoints/data.py
Comment thread backend/ibex/data_source/imas_python_source_utils.py Outdated
@jwasikpsnc jwasikpsnc marked this pull request as draft June 3, 2026 10:25
@jwasikpsnc
Copy link
Copy Markdown
Collaborator Author

jwasikpsnc commented Jun 3, 2026

  • Allow to smooth 2D quantities when one of the coordinate is time

@jwasikpsnc jwasikpsnc marked this pull request as ready for review June 5, 2026 11:41
@jwasikpsnc
Copy link
Copy Markdown
Collaborator Author

@olivhoenen
Now it is ready for further review

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

Successfully merging this pull request may close these issues.

2 participants