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
This is just a heads up, since I forked LIME awhile ago to make some changes specific to my application and haven't merged updates in the last year or so... Maybe you've fixed this. But if you haven't come across this potential error yet:
It's possible for create_lh_list to make a Mat_l vector that's shorter than the user-specified length-frequency data dimension. It uses 1.3*linf as the max length, and there's no check for what the user's max length in the LF data is. I stumbled across it when I kept everything (data, model, code) the same except with a lower linf and higher vbk... was surprised it wouldn't run.
Not urgent - I just changed my local create_lh_list to use 1.4*linf for now.
The text was updated successfully, but these errors were encountered:
Hi Merrill,
This is just a heads up, since I forked LIME awhile ago to make some changes specific to my application and haven't merged updates in the last year or so... Maybe you've fixed this. But if you haven't come across this potential error yet:
It's possible for
create_lh_list
to make aMat_l
vector that's shorter than the user-specified length-frequency data dimension. It uses1.3*linf
as the max length, and there's no check for what the user's max length in the LF data is. I stumbled across it when I kept everything (data, model, code) the same except with a lower linf and higher vbk... was surprised it wouldn't run.Not urgent - I just changed my local
create_lh_list
to use1.4*linf
for now.The text was updated successfully, but these errors were encountered: