TINTOlib 1.2.0__tar.gz → 1.2.2__tar.gz

{tintolib-1.2.0 → tintolib-1.2.2}/.gitignore

@@ -1,168 +1,170 @@
-**/__pycache__
-=======
-#Misc
-HyNNImages/
-logs/
-data/
-scripts_logs/
-
-# Byte-compiled / optimized / DLL files
-__pycache__/
-*.py[cod]
-*$py.class
-
-# C extensions
-*.so
-
-# Distribution / packaging
-.Python
-build/
-develop-eggs/
-dist/
-downloads/
-eggs/
-.eggs/
-lib/
-lib64/
-parts/
-sdist/
-var/
-wheels/
-share/python-wheels/
-*.egg-info/
-.installed.cfg
-*.egg
-MANIFEST
-
-# PyInstaller
-#  Usually these files are written by a python script from a template
-#  before PyInstaller builds the exe, so as to inject date/other infos into it.
-*.manifest
-*.spec
-
-# Installer logs
-pip-log.txt
-pip-delete-this-directory.txt
-
-# Unit test / coverage reports
-htmlcov/
-.tox/
-.nox/
-.coverage
-.coverage.*
-.cache
-nosetests.xml
-coverage.xml
-*.cover
-*.py,cover
-.hypothesis/
-.pytest_cache/
-cover/
-
-# Translations
-*.mo
-*.pot
-
-# Django stuff:
-*.log
-local_settings.py
-db.sqlite3
-db.sqlite3-journal
-
-# Flask stuff:
-instance/
-.webassets-cache
-
-# Scrapy stuff:
-.scrapy
-
-# Sphinx documentation
-docs/_build/
-
-# PyBuilder
-.pybuilder/
-target/
-
-# Jupyter Notebook
-.ipynb_checkpoints
-
-# IPython
-profile_default/
-ipython_config.py
-
-# pyenv
-#   For a library or package, you might want to ignore these files since the code is
-#   intended to run in multiple environments; otherwise, check them in:
-# .python-version
-
-# pipenv
-#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
-#   However, in case of collaboration, if having platform-specific dependencies or dependencies
-#   having no cross-platform support, pipenv may install dependencies that don't work, or not
-#   install all needed dependencies.
-#Pipfile.lock
-
-# poetry
-#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
-#   This is especially recommended for binary packages to ensure reproducibility, and is more
-#   commonly ignored for libraries.
-#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
-#poetry.lock
-
-# pdm
-#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
-#pdm.lock
-#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
-#   in version control.
-#   https://pdm.fming.dev/#use-with-ide
-.pdm.toml
-
-# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
-__pypackages__/
-
-# Celery stuff
-celerybeat-schedule
-celerybeat.pid
-
-# SageMath parsed files
-*.sage.py
-
-# Environments
-.env
-.venv
-env/
-venv/
-ENV/
-env.bak/
-venv.bak/
-
-# Spyder project settings
-.spyderproject
-.spyproject
-
-# Rope project settings
-.ropeproject
-
-# mkdocs documentation
-/site
-
-# mypy
-.mypy_cache/
-.dmypy.json
-dmypy.json
-
-# Pyre type checker
-.pyre/
-
-# pytype static type analyzer
-.pytype/
-
-# Cython debug symbols
-cython_debug/
-
-# PyCharm
-#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
-#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
-#  and can be added to the global gitignore or merged into this file.  For a more nuclear
-#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
-.idea/
+# Misc
+.DS_Store
+HyNNImages/
+SyntheticImages/
+logs/
+data/
+scripts_logs/
+objs.pkl
+
+# Byte-compiled / optimized / DLL files
+**/__pycache__/
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/#use-with-ide
+.pdm.toml
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+.idea/

{tintolib-1.2.0 → tintolib-1.2.2}/CITATION.cff

@@ -1,39 +1,39 @@
-cff-version: 1.2.0
-message: "If you use TINTOlib or this article, please cite it as below."
-title: "TINTOlib: A Python library for transforming tabular data into synthetic images for deep neural networks"
-version: "1.0.6.1"
-license: "Apache-2.0"
-type: "article"
-doi: "10.1016/j.softx.2025.102444"
-authors:
-  - family-names: "Liu"
-    given-names: "Jiayun"
-    affiliation: "Universidad Politécnica de Madrid"
-  - family-names: "González-Fernández"
-    given-names: "David"
-    affiliation: "Universidad Politécnica de Madrid"
-  - family-names: "Castillo-Cara"
-    given-names: "Manuel"
-    affiliation: "Universidad Nacional de Educación a Distancia (UNED), Instituto de Investigación Científica - Universidad de Lima"
-    orcid: "https://orcid.org/0000-0002-2990-7090"
-  - family-names: "García-Castro"
-    given-names: "Raúl"
-    affiliation: "Universidad Politécnica de Madrid"
-    orcid: "https://orcid.org/0000-0002-0421-452X"
-preferred-citation:
-  type: "article"
-  title: "TINTOlib: A Python library for transforming tabular data into synthetic images for deep neural networks"
-  authors:
-    - family-names: "Liu"
-      given-names: "Jiayun"
-    - family-names: "González-Fernández"
-      given-names: "David"
-    - family-names: "Castillo-Cara"
-      given-names: "Manuel"
-    - family-names: "García-Castro"
-      given-names: "Raúl"
-  journal: "SoftwareX"
-  year: 2025
-  volume: 32
-  doi: "10.1016/j.softx.2025.102444"
+cff-version: 1.2.0
+message: "If you use TINTOlib or this article, please cite it as below."
+title: "TINTOlib: A Python library for transforming tabular data into synthetic images for deep neural networks"
+version: "1.0.6.1"
+license: "Apache-2.0"
+type: "article"
+doi: "10.1016/j.softx.2025.102444"
+authors:
+  - family-names: "Liu"
+    given-names: "Jiayun"
+    affiliation: "Universidad Politécnica de Madrid"
+  - family-names: "González-Fernández"
+    given-names: "David"
+    affiliation: "Universidad Politécnica de Madrid"
+  - family-names: "Castillo-Cara"
+    given-names: "Manuel"
+    affiliation: "Universidad Nacional de Educación a Distancia (UNED), Instituto de Investigación Científica - Universidad de Lima"
+    orcid: "https://orcid.org/0000-0002-2990-7090"
+  - family-names: "García-Castro"
+    given-names: "Raúl"
+    affiliation: "Universidad Politécnica de Madrid"
+    orcid: "https://orcid.org/0000-0002-0421-452X"
+preferred-citation:
+  type: "article"
+  title: "TINTOlib: A Python library for transforming tabular data into synthetic images for deep neural networks"
+  authors:
+    - family-names: "Liu"
+      given-names: "Jiayun"
+    - family-names: "González-Fernández"
+      given-names: "David"
+    - family-names: "Castillo-Cara"
+      given-names: "Manuel"
+    - family-names: "García-Castro"
+      given-names: "Raúl"
+  journal: "SoftwareX"
+  year: 2025
+  volume: 32
+  doi: "10.1016/j.softx.2025.102444"
   url: "https://doi.org/10.1016/j.softx.2025.102444"