Yes that is a good idea. I wasn't thinking about using these measurements in this way when I made them. Anotherr way to get around this could be to band pass the IR. I have done this before. Of course, that won't fix the issue of the window being in the wrong place!The peak of the result IR was outside the range and got chosen as the ref. The large artefacts outside the valid part of the result are caused by starting the measurements at a relatively high frequency (30 Hz) and ending the ref measurement at a very low frequency (300 Hz) that is also much lower than the span of the other measurements. Here is the relevant help section on how REW handles that:
The frequency span of the result of an arithmetic operation will be from the lowest start frequency to the highest end frequency of the traces operated on. Outside their frequency range traces are treated as being zero valued, with the exception of the divisor in a division operation which is treated as being unity outside its range. If the measurements actually have significant levels outside the measurement range the zero setting will generate oscillations in frequency and time domains, for best results use traces that span the full frequency range.
I'd suggest starting the measurements at zero and ending both reference and actual at the same frequency.
I wonder if there might be a way to gracefully return the numerator to zero outside the measurement bandwidth??