Classical-mf-structure

Revision as of 17:26, 14 October 2015

Structure of the modular_forms folder:

• backend
  • __init__.py
  • mf_classes.py: defines two classes. ??? The 1st one should contain a (dimension?) table obtained from the DB, the 2nd one should contain a single modular form obtained from the DB. ???
  • mf_utils.py
• elliptic_modular_forms
  • __init__.py
  • test_emf.py
  • backend
    • __init__.py
    • emf_classes.py
    • emf_core.py
    • emf_download_utils.py
    • emf_utils.py
    • experimental !!!! (empty)
    • web_newforms.py
    • web_object.py
    • plot_dom.py
    • web_character.py
    • web_modform_space.py
  • views
    • __init__.py
    • emf_render_navigation.py
    • emf_render_web_modform_space.py
    • experimental !!!! (empty)
    • emf_render_web_newform.py
    • emf_main.py
    • emf_render_web_modform_space_gamma1.py
    • static ???? Probably not used (deleting it does not seem to break anything)
      • elliptic_modular_form_scripts.js ????
      • elliptic_modular_form_util-functions.js ????
    • templates
      • emf_browse_fixed_level.html
      • emf_navigation.html
      • emf_table.html
      • emf_web_newform.html
      • geometric.html
      • select_ranges.html
      • emf_browse_spaces.html
      • emf_render_web_modform_space_gamma1.html
      • emf_web_modform_space.html
      • not_available.html
      • experimental !!!!
        • data_table.html
        • emf2.html
        • emf_browse.html
        • emf_browse_graph.html
        • emf_browse_range.html
        • emf_new.html
        • emf_table2.html
• maass_forms
  • ...
• views
  • __init__.py
  • mf_main.py
  • templates
    • mf_navigation.html