Is your feature request related to a problem? Please describe.
I would like to try using plassembler with dragonflye outputs, without wasting compute on rerunning flye in plassembler.

Describe the solution you'd like
Would it be feasible to allow e.g.

--flye_assembly /scratch/$USER/out/d58_unidragonflye_m180/NN-MR49-2_all_merge_dflye_m180p_out_job63789870/flye.fasta
--flye_info /scratch/$USER/out/d58_unidragonflye_m180/NN-MR49-2_all_merge_dflye_m180p_out_job63789870/flye-info.txt

rather than having to rerun flye or make temp copies hopefully-concordant with standard flye output e.g.

[user@ccs0050(hawk) NN-MR49-2_all_merge_dflye_m180p_out_job63789870]$ mkdir temp_plassembler/
[user@ccs0050(hawk) NN-MR49-2_all_merge_dflye_m180p_out_job63789870]$ cp flye.fasta temp_plassembler/assembly.fasta
[user@ccs0050(hawk) NN-MR49-2_all_merge_dflye_m180p_out_job63789870]$ cp flye-info.txt temp_plassembler/assembly_info.txt
[...]

...for --flye_directory

Describe alternatives you've considered
Perhaps this is the alternative (to what I currently do, follow up every dragonflye-mediated flye assembly with a full unicycler assembly)?

Thanks for openly sharing your plasmid recovery tool, either way!