Sergey Aganezov

Hi Andre, thank you for your interest in `CAMSA`. The core of `CAMSA` (i.e., the scaffolding merging/comparative analysis does not use any of the parallelization techniques, as even on large...

Hello @rob123king, and I'm sorry that you've experienced the issue with CAMSA. Please try to use the `=` sign to assign name parameters in the script invocation. You example then...

Hello, and thank you for your interest in `CAMSA`! First thing first, please make sure you are running the latest version of `CAMSA`. Now to the problem. First, if you...

@francicco Great to hear that the problem went away. Please also note the part of my response w.r.t. `CAMSA` expectations about the input assemblies, contigs, etc. And let me know...

@francicco Yeah, I believe, I understand your situation. `CAMSA` was primarily designed to merge multiple **scaffold** assemblies, where every scaffold assembly is build on the same set of contigs. Imaging...

That is correct! Then, with such "alignments" in `contigs.fasta`, the regular `CAMSA` pipeline will be feasible.

So I don't think you need the actual alignment positions of common contigs, just the contigs themselves (alignment positions would be identified by `CAMSA` `fasta2camsa_points.py` pipeline). If you can get...

Hello @francicco , thank for posting this! the `std:bad_alloc` is most likely coming from the mummer itself, not CAMSA utils. Can you, please, check, that the `mummer` works fine on...

hello @francicco So, alignment indeed takes quite a while. It's a very computationally intensive process, and, while MUMmer is a well designed software, there is nothing I can do to...

Hello @daneshnedaie , is your question related to the issue described above? If not, I would suggest (for the future) that you open a separate issue with your question. With...