What are the main benefits of MUSICX versus MUSIC 6.3.0?

MUSICX has been re-designed and re-written into modern software coding platform, maintaining all the capability of MUSIC V6.3 but gives users additional functionality and the benefits of modern software architecture.

In the present release, MUSICX allows you to combine your MUSIC models with eWater Source (and the new Source plugin - Urban Developer) to model both water quality and quantity.  A limitation is that MUSICX and Source will have to run at the same time step. We are working on providing a solution where the three models will be able to run at different times steps, appropriate to the scale of the different tools. This will ultimately give  you the tools to design truly integrated water resource management solutions.  

The new coding platform brings the ability to customize your MUSICX models by developing plugins. Plugins can be written for a wide range of purposes, including to incorporate or test new treatment options, add new contaminants, recognize local features, such as soil type and hydrology or to include new science. Compatibility with the Source platform also allows you to access Source plugins, such as additional Rainfall-Runoff models.

MUSICX also brings the benefits of:

·        Improved Graphic User Interface for easy data input, tabular input/output, group edit and advanced graphics.

·        Function Manager to support more complex model building.

·        Powerful in-built Results Manager for data analysis and results interpretation.

Products - MUSIC X

  1. What are the main benefits of MUSICX versus MUSIC 6.3.0?
  2. What new opportunities will MUSICX support?
  3. Does MUSICX have any new capability or science?
  4. How can unique or local conditions be incorporated?
  5. How do I write a plugin?
  6. Licensing, pricing and support
  7. Compatibility between MUSICX and MUSIC 6.3 and transitioning to MUSICX
  8. Is MUSIC-link available?
  9. Does MUSICX have Source functionality like inbuilt calibration and optimisation?
  10. Has the "edit all nodes of this type" functionality been retained?
  11. Does MUSICX have the ability to model sub-timestep scale routing along MUSIC links?
  12. Have extra routing models been added other than ‘none’, ‘translation’ and ‘muskingum-cunge’ that are in MUSIC 6.3?
  13. When you run a grassed swale in MUSIC 6.3 it has 100% removal efficiency for gross pollutants. The performance of the swale is also the same, regardless of whether it is 2% grade or 15% grade. Is this fixed in MUSICX?
  14. Does the flow transfer function within a generic node still ‘loose’ water from the model, or can I now account for this ‘lost’ water within a secondary link?
  15. Have the source node input properties been changed from MUSIC 6.3 or are many of the Source nodes still the same (residential, commercial, industrial) with the only variation in the nodes being their name?
  16. When a file is sent to a regulator to review, will it include the met-data or will they have to specify it separately?
  17. Do secondary links exist in MUSICX?
  18. Previous versions of MUSIC were not well accepted for use in WA due to unique soil conditions in the Swan Coastal Plain. Will MUSIC X be compatible for use in WA?
  19. How does the program know how to read the rainfall xls? Does it need to be in particular column etc. or can it work it out for itself?
  20. Has the MUSIC 6.3 bug relating to a maximum custom storage depth within a wetland been fixed

Feedback and Knowledge Base