<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="en-BE">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Dear all,</span><span lang="en-BE"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> </span><span lang="en-BE"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I have an EEG dataset that consists of quite long trials (>20s). Therefore, For artifact rejection I would like to only reject the part of the trial that contains the artifact, rather than throwing away the entire trial,
and thus I will use the cfg.artfctdef.method = ‘partial’; option in ft_rejectartifact.</span><span lang="en-BE"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">However, this leads to some trials being cut in two shorter “trials” (i.e., the part before the artifact and the part after the artifact). I’m guessing this will lead to edge artifacts in my time-frequency analysis, not
only at the edges of the original trials, but also at time points where artifacts were cut out. SO I’m not sure how to deal with this.</span><span lang="en-BE"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> </span><span lang="en-BE"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">I guess one option would be to perform the time-frequency analysis first, and afterwards cut out the artifacts, although (1) that might lead to the artifact smearing into data points that were not cut out, depending on
the time window width during frequency analysis, and (2) the artifacts identified visually using ft_databrowser are define din ample numbers, and the result from ft_freqanalysis downsamples the data.</span><span lang="en-BE"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"> </span><span lang="en-BE"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Did anyone face similar issues or have ideas on how to get around this?</span><span lang="en-BE"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-BE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-BE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-BE"><br>
________________________________________<br>
Matthias Franken<br>
postdoctoral researcher<br>
Experimental Psychology Department<br>
Ghent University<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-BE"><o:p> </o:p></span></p>
</div>
</body>
</html>