EVN Observation Planner. Helps you to plan a VLBI observation. Given a date, source coordinates, and a VLBI array, it will tell you when the source can be observed by each antenna, the reached rms noise level and resolution, among other details.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 

90 lines
4.4 KiB

  1. from setuptools import setup
  2. from setuptools import find_packages
  3. import pathlib
  4. # Get the long description from the README file
  5. long_description = (pathlib.Path(__file__).parent.resolve() / 'README.md').read_text(encoding='utf-8')
  6. setup(name='vlbiplanobs',
  7. # Versions should comply with PEP 440:
  8. # https://www.python.org/dev/peps/pep-0440/
  9. # [N!]N(.N)*[{a|b|rc}N][.postN][.devN]
  10. version='2.0.3',
  11. # one-line description or tagline of what your project does
  12. description='Planner for VLBI observations',
  13. # "Description" metadata field
  14. long_description=long_description,
  15. long_description_content_type='text/markdown',
  16. url='https://github.com/bmarcote/vlbi_calculator',
  17. download_url='https://github.com/bmarcote/vlbi_calculator/tarball/2.0.3',
  18. author='B. Marcote',
  19. author_email='marcote@jive.eu',
  20. # Classifiers help users find your project by categorizing it.
  21. # For a list of valid classifiers, see https://pypi.org/classifiers/
  22. classifiers=[ # Optional
  23. # How mature is this project? Common values are
  24. # 3 - Alpha
  25. # 4 - Beta
  26. # 5 - Production/Stable
  27. 'Development Status :: 5 - Production/Stable',
  28. # Indicate who your project is intended for
  29. 'Intended Audience :: Science/Research',
  30. 'Topic :: Scientific/Engineering :: Astronomy',
  31. # Pick your license as you wish
  32. 'License :: OSI Approved :: GNU Lesser General Public License v3 or later (LGPLv3+)',
  33. # Specify the Python versions you support here. In particular, ensure
  34. # that you indicate you support Python 3. These classifiers are *not*
  35. # checked by 'pip install'. See instead 'python_requires' below.
  36. 'Programming Language :: Python :: 3',
  37. 'Programming Language :: Python :: 3.7',
  38. 'Programming Language :: Python :: 3.8',
  39. 'Programming Language :: Python :: 3 :: Only',
  40. ],
  41. keywords='astronomy, astrophysics, cosmology, radio, science, observations, planner, coordinate',
  42. python_requires='>=3.7, <4',
  43. # When your source code is in a subdirectory under the project root, e.g.
  44. # `src/`, it is necessary to specify the `package_dir` argument.
  45. # package_dir={'': 'src'}, # Optional
  46. packages=find_packages(),
  47. scripts=['bin/vlbiplanobs'],
  48. # This field lists other packages that your project depends on to run.
  49. # Any package you put here will be installed by pip when your project is
  50. # installed, so they must be valid existing projects.
  51. #
  52. # For an analysis of "install_requires" vs pip's requirements files see:
  53. # https://packaging.python.org/en/latest/requirements.html
  54. install_requires=['numpy', 'astropy>=4.0.2', 'astroplan>=0.7'],
  55. # If there are data files included in your packages that need to be
  56. # installed, specify them here.
  57. package_data={
  58. 'stations': ['data/stations_catalog.inp'],
  59. 'docs': ['docs/*'],
  60. 'assets': ['assets/*']
  61. },
  62. # Although 'package_data' is the preferred approach, in some case you may
  63. # need to place data files outside of your packages. See:
  64. # http://docs.python.org/distutils/setupscript.html#installing-additional-files
  65. #
  66. # In this case, 'data_file' will be installed into '<sys.prefix>/my_data'
  67. # data_files=[('data', ['data/stations_catalog.inp'])],
  68. include_package_data=True,
  69. # List additional URLs that are relevant to your project as a dict.
  70. #
  71. # This field corresponds to the "Project-URL" metadata fields:
  72. # https://packaging.python.org/specifications/core-metadata/#project-url-multiple-use
  73. #
  74. # Examples listed include a pattern for specifying where the package tracks
  75. # issues, where the source is hosted, where to say thanks to the package
  76. # maintainers, and where to support the project financially. The key is
  77. # what's used to render the link text on PyPI.
  78. project_urls={ # Optional
  79. 'Bug Reports': 'https://github.com/bmarcote/vlbi_calculator/issues',
  80. # 'Funding': 'https://donate.pypi.org',
  81. # 'Say Thanks!': 'http://saythanks.io/to/example',
  82. 'Source': 'https://github.com/bmarcote/vlbi_calculator/',
  83. },
  84. )