Null Genomes Make Problems in Using Galapagos

Hello, I have a problem that I hope someone here can help me with
To have a shorter simulation time to check different alternatives, I wrote an algorithm that rejects null in some cases and works perfectly in brute-force cases.
But when I use the Galapagos component to check a higher number of variables, I get into trouble, and after 9 hours of optimization, only those that were null and should have been excluded from the calculations get better answers!


Please guide me to find a way to solve this problem so that if any of Genomes is null, it will remove it from the optimal options.
Also, I used Data Recorder to save the checked modes in Galapagos, but Date Recorder also saved null answers in a separate branch and messed up the order of the list. Therefore, in this way, I could not understand the best ways to work from the list because the order of the genome list with nulls was recorded correctly, but in the fitness list, the nulls were moved to another branch and separated.

Please guide me if anyone knows the solution so that I can solve the problem :pray:

Replace nulls with a sub-optimal fitness value so that they are rejected by Galapagos.

@grbl9789 Thanks for your guidance :pray: