Here are some posts that discuss read length and depth in rMATS:
https://groups.google.com/g/rmats-user-group/c/hpr7j9FMgFg/m/M9qbjIYJAgAJhttps://groups.google.com/g/rmats-user-group/c/hgEOH_b5Pr0/m/KqyKUfevAAAJhttps://github.com/Xinglab/rmats-turbo/issues/83
If you process each dataset separately, you can use --fixed-event-set to run each dataset with the appropriate --readLength value. rMATS uses the read length as part of the IncLevel (PSI value) calculation:
https://github.com/Xinglab/rmats-turbo/issues/349Because of the normalization, the PSI values should be reasonable to compare across datasets
Instead, if you run both datasets in the same post step, then the rMATS statistical model will consider the read counts when checking for significant splicing events. The higher read depth would generally lead to higher confidence in the PSI value for that group and lead to more significant pvalues. When running both datasets together, a single read length has to be provided and the PSI value calculation won't be ideal
You could try downsampling the higher read depth dataset. You could also try truncating each read in the longer read length dataset. Reducing to the minimum value might make the datasets more comparable
Eric