Right now, testing a custom candidate (e.g. a user-specified period and epoch) is a pain, requiring manually editing the saved phased candidate IDL structure. Write an IDL function that allows the user to specify a period and epoch, and enter it into the MITTENS database. The cleanest way to do this would be to have a separate phased candidates IDL save file for the custom candidates, which will have to be loaded by "load_summary_of_candidates" and "inspect", to display to the user.
Right now, testing a custom candidate (e.g. a user-specified period and epoch) is a pain, requiring manually editing the saved phased candidate IDL structure. Write an IDL function that allows the user to specify a period and epoch, and enter it into the MITTENS database. The cleanest way to do this would be to have a separate phased candidates IDL save file for the custom candidates, which will have to be loaded by "load_summary_of_candidates" and "inspect", to display to the user.