I changed the chunksize to accept 0 which will not split the file. This is important to those running on a cluster where the amount of jobs are defined by the scheduler. For instance, if I submit a job to slurm and do not specify how many cpus it can use, abstar will split the file based on the chunksize and use as many as fifty different jobs. The jobs were not specified by the scheduler, so it will clash with other jobs running on the cluster. It is much easier to split the fasta files outside of the cluster, then run each one a seperate job. This will probably only need to be termporary until I can maybe write some code within abstar to submit jobs to a cluster via slurm or torque API.
I changed the chunksize to accept 0 which will not split the file. This is important to those running on a cluster where the amount of jobs are defined by the scheduler. For instance, if I submit a job to slurm and do not specify how many cpus it can use, abstar will split the file based on the chunksize and use as many as fifty different jobs. The jobs were not specified by the scheduler, so it will clash with other jobs running on the cluster. It is much easier to split the fasta files outside of the cluster, then run each one a seperate job. This will probably only need to be termporary until I can maybe write some code within abstar to submit jobs to a cluster via slurm or torque API.

briney/abstar