Added new Examples - #253
Conversation
…and asymmetric_peak_map function, added data tests directory and created a test for both functions
…umiSpy#250 and made nanoparticles.hspy significantly smaller
…and asymmetric_peak_map function, added data tests directory and created a test for both functions
…umiSpy#250 and made nanoparticles.hspy significantly smaller
| ax1 = s2.axes_manager[0] | ||
| ax2 = s2.axes_manager[1] | ||
|
|
||
| # define start params |
There was a problem hiding this comment.
Can a units argument be used here to avoid multiplying by scale factors? I think if cx, cy were not defined the default position of the circle should also place within the bounds of the signal
There was a problem hiding this comment.
Yes we could also just leave it out completly the cx, cy and r part but the result then wouldn't be quite as good, this just the only way to show it interactively how you would then choose the area without being able to actually choose. Tho for simple demonstration of the Circle roi i could be left out.
There was a problem hiding this comment.
HyperSpy does have a nice example gallery for ROIs already, in order to not overlap too much I wonder if these examples can be a little more specific to luminescence data analysis. One thing I think could also be included is a computation of calculating the mean of a signal extracted from a ROI - though this is also included in a hyperspy example
There was a problem hiding this comment.
These examples are nice but I wonder if they would be more suited to the HyperSpy example gallery? They don't seem specific to luminescence data, one idea would be to keep the Mathematical Expression header but define a exponential convolved with a gaussian (since this is useful for modelling time-resolved luminescence transients)
There was a problem hiding this comment.
Maybe also better suited as a hyperspy example?
I don't love that the ohaver function returns a structured array instead of hyperspy signals, if this was changed I think it would make this example better as well.
There was a problem hiding this comment.
We should probably push to get this PR done and include a way to return data as signal: hyperspy/hyperspy#3196
There was a problem hiding this comment.
The Line2D ROI example also appears under Plotting - Extraction of Linescan example
There was a problem hiding this comment.
Should i then just leave it out and maybe add a different roi and link to the extraction of linescan example for usage of rois like the Line2D
eecb913 to
727dbf1
Compare
There was a problem hiding this comment.
We should probably push to get this PR done and include a way to return data as signal: hyperspy/hyperspy#3196
| # Indexing using Physical units | ||
| # ----------------------------- | ||
| # | ||
| # Hyperspy supports indexing with physical units (floating-point) values when the |
There was a problem hiding this comment.
The explanation here is a bit complicated ... you only need to change the scale in this example, because otherwise the axis values are integers. On the other hand, the example with [0:np.pi] actually does indexing using physical units already - so maybe use that one to explain the concept?
55776bb to
beed5d1
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #253 +/- ##
===========================
===========================
☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Added new example map_function, energie_conversion, ROIs, peak_analysis, basic_model_fitting, custom_model_fitting and restructured the old position of the index example. And changed all the data_cleaning examples to use the build in data module of lumispy
Progress of the PR
upcoming_changesfolder ,