Include TransducerArrays in standardize_database script (#337)

Removes the stale TransducerArray skip. Since openlifu-python commit
cbd521b introduced TransducerArray with its own to_file, and
Database.write_transducer is type-agnostic and just calls
transducer.to_file(...), the skip is no longer needed.

Author: ebrahimebrahim

examples/tools/standardize_database.py

@@ -1,11 +1,11 @@
-"""This is a utility script for developers to read in and write back out the dvc database.
-It is useful for standardizing the format of the example dvc data, and also for checking that the database
+"""This is a utility script for developers to read in and write back out an openlifu database.
+It is useful for standardizing the format of the example data, and also for checking that the database
 mostly still works.
 
 To use this script, install openlifu to a python environment and then run the script providing the database folder as an argument:
 
 ```
-python standardize_database.py db_dvc/
+python standardize_database.py /path/to/openlifu-sample-database
 ```
 
 A couple of known issues to watch out for:
@@ -15,15 +15,13 @@
 """
 from __future__ import annotations
 
-import logging
 import pathlib
 import shutil
 import sys
 import tempfile
 
 from openlifu.db import Database
 from openlifu.db.database import OnConflictOpts
-from openlifu.xdc import Transducer
 
 if len(sys.argv) != 2:
     raise RuntimeError("Provide exactly one argument: the path to the database folder.")
@@ -38,9 +36,6 @@
 db.write_transducer_ids(db.get_transducer_ids())
 for transducer_id in db.get_transducer_ids():
     transducer = db.load_transducer(transducer_id, convert_array=False)
-    if not isinstance(transducer, Transducer):
-        logging.warning(f"Skipping {transducer_id} because TransducerArray writing is not supported.")
-        continue
     assert transducer_id == transducer.id
     db.write_transducer(transducer, on_conflict=OnConflictOpts.OVERWRITE)