Closed alexdewar closed 2 months ago
Yes, but I think we need to rethink this. One of the seasons might have a different number of sub-slices. So shouldn't it be three columns - season, daynight, value Like: winter, peak, 0.03125
Ahh ok! I didn't realise that. I'll open another issue for that bug
See also #69
FYI @Ashmit8583 @abhinavgupta2004 I'm working on this now, so don't do anything on this front.
Sure sir . Thank you for the update
On Tue, 25 Jun 2024, 10:55 am Alex Dewar, @.***> wrote:
FYI @Ashmit8583 https://github.com/Ashmit8583 @abhinavgupta2004 https://github.com/abhinavgupta2004 I'm working on this now, so don't do anything on this front.
— Reply to this email directly, view it on GitHub https://github.com/EnergySystemsModellingLab/MUSE_2.0/issues/59#issuecomment-2188474992, or unsubscribe https://github.com/notifications/unsubscribe-auth/BAWEAH5FWGEOYIPUCYXHS5TZJE5CZAVCNFSM6AAAAABJEOOQSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBYGQ3TIOJZGI . You are receiving this because you were mentioned.Message ID: @.***>
This file contains information about the way in which time is divided up in the simulation.
@ahawkes Am I right in thinking that the seasons and times of day should be user configurable (i.e. that they can supply arbitrary row and column names)?