segment: CDR3/Junction JSON output could be falsely set
When JUNCTIONstart or JUNCTIONend equaled 0, their values were not modified. But the CDR3/Junction are output in the JSON as long as the values of the variables are >= 0 (maybe this should also have been modified). Therefore we could have weird results with JUNCTIONstart=0 and JUNCTIONend=40. Tests added.
Showing with 16 additions and 1 deletion