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
Hi all, I ran scarHRD normally for my seqz files.I've been getting this error. I updated my R and R studio. I also increased my Vroom connection size as Sys.setenv(VROOM_CONNECTION_SIZE = 131072*3), still I'm getting this error
The error is as follows:
Preprocessing started...
Collecting GC information ............... done
Processing chr1:
7 variant calls.
3 copy-number segments.
397 heterozygous positions.
793879 homozygous positions.
Processing chr2:
Error: The size of the connection buffer (393216) was not large enough
to fit a complete line:
Increase it by setting Sys.setenv("VROOM_CONNECTION_SIZE")
In addition: There were 50 or more warnings (use warnings () to see the first 50)
Also, if I increase the size VROOM_CONNECTION_SIZE = 131072*10000), Im facing this error.
Processing chr1:
Error: cannot create std:vector larger than max_size()
Kindly anyone helpme in this!!
The text was updated successfully, but these errors were encountered:
Hi all, I ran scarHRD normally for my seqz files.I've been getting this error. I updated my R and R studio. I also increased my Vroom connection size as Sys.setenv(VROOM_CONNECTION_SIZE = 131072*3), still I'm getting this error
The error is as follows:
Preprocessing started...
Collecting GC information ............... done
Processing chr1:
7 variant calls.
3 copy-number segments.
397 heterozygous positions.
793879 homozygous positions.
Processing chr2:
Error: The size of the connection buffer (393216) was not large enough
to fit a complete line:
Sys.setenv("VROOM_CONNECTION_SIZE")
In addition: There were 50 or more warnings (use warnings () to see the first 50)
Also, if I increase the size VROOM_CONNECTION_SIZE = 131072*10000), Im facing this error.
Processing chr1:
Error: cannot create std:vector larger than max_size()
Kindly anyone helpme in this!!
The text was updated successfully, but these errors were encountered: