You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Python/02-GroupPSDs, the sub-selection of frequency ranges (under the 'Tuning the specparam algorithm' section) could use the trim_spectrum utility, which would be a little cleaner
In the Python notebooks, use a output_path = Path('../Output/') like is done for the data_path
PEP8 spacing updates: should be no space after argument assignment (eg function(a=1) not function(a = 1)).
R files:
Updated Python code in the R markdown files to match any updates made in the Python files
Update line length of text lines (these can be wrapped right?)
Check and fix spacing*
*Is there a standard spacing guideline for R? One thing I find a bit visually weird is the uneven spaces around assignements within function calls (ex: function(arg= val) as opposed to func(arg=val) or func(arg = val). Looking at this guide, I think the convention would be to have a space either side, so if it's all the same, I'd update to that.
The text was updated successfully, but these errors were encountered:
Minor potential tweaks to the repository files.
Python files:
output_path = Path('../Output/')
like is done for thedata_path
function(a=1)
notfunction(a = 1)
).R files:
*Is there a standard spacing guideline for R? One thing I find a bit visually weird is the uneven spaces around assignements within function calls (ex:
function(arg= val)
as opposed tofunc(arg=val)
orfunc(arg = val)
. Looking at this guide, I think the convention would be to have a space either side, so if it's all the same, I'd update to that.The text was updated successfully, but these errors were encountered: