Redundant zeros in config.json and profiled_HEAAN_GPU.json?

[Tokubara]

Redundant initial zeros in latencyTable operations?

In config.json (and other configuration JSON files), all operations in latencyTable start with 0. Here's a snippet from config.json:

  "earth.add_double": [
   0, 3, 3, 3, 3,
   3, 3, 3, 3, 3,
   3, 3, 3, 3, 3,
   3, 6
  ],

However, in setCKKSParameters(), a 0 is already pushed to latencyTable:

      latTab.push_back(0);

This ensures that all operations have a latency of 0 at level 0. Are the initial zeros in config.json and similar files redundant?

Extra zeros in "earth.bootstrap_single" latencyTable?

In profiled_HEAAN_GPU.json, "earth.bootstrap_single" in latencyTable starts with 4 zeros:

  "earth.bootstrap_single": [
   0,
   0,
   0,
   0,
   294928,

Given that bootstrapLevelLowerBound is set to 3:

 "bootstrapLevelLowerBound": 3,

This implies "earth.bootstrap_single" should have values greater than 0 starting from level 3. Considering the aforementioned push_back(0) in setCKKSParameters(), should "earth.bootstrap_single" only start with 2 zeros (for levels 1 and 2) instead of 4?