As @selene says, if you do this you will have to use paged sound windows to avoid memory management problems. See Chapter 7 in the Raven Pro User's Manual.

When a selection table is opened as a sound selection table, Raven opens all the sound files listed in "Begin Path" and uses the "Begin Path" and "File Offset" fields as the primary time reference to determine selection bounds. It will also overwrite the values in the "Begin Time" and "End Time" fields. BTW, if you merge several selection tables using a text editor, all the selection tables must have all the same fields in the same order. You must also remove the header line for every selection table except the one in line 1.

@selene has a solution that will work. If the selection table has the "Begin Path" and "File Offset" measurement, it can be opened as a "Sound Selection Table". A sound selection table can be opened into the blue field in Raven by (1) File > Open Sound Selection Table or (2) Hold the CTRL key while dragging and dropping into the blue field

The problem with the precision-recall curve is the use of precision, which is correlated with the abundance of the target signal. If the target signal is abundant, even a bad detector can achieve a high precision. Conversely, if the target signal is rare, precision can be low even with a very good detector. This shortcoming can be mitigated by using a statistic for reporting false positives that is less correlated with abundance, like number of false positives per unit time, which provides an estimate of type II error that is less confounded by the abundance of the target signal.

The theoretical underpinning of Raven's "robust signal measurements" can be found in Fristrup and Watkins (1992) and Fristrup and Watkins (1994).

The most commonly used reference pressure for media other than gases is 1µPa. See ASA reference value for sound pressure.