File structure for test problems and data

[dowonlee777]

Hi Jeremy,

To organize our file structure for the new test problems and analysis, here's what I am thinking:

• 1. CLPSSitesRandomSats data (Visibility data for CLPS sites)

  • Add all orbits that you used for the genetic algorithm
  • Remove "Random" from CLPSSitesRandomSats folder name. (e.g. CLPSSitesVis)

• 2. New folder named test_problems with the following structure

   test_problems/
        T_fin_192.0_dt_30.0_site_locs_((1,30),(3,30))/    # Same naming pattern
             3_3/    # <number blue>_<number red>  
                 # The following folders are the same as you did with the "BLUE" and "RED" folders in "AllConstellations".
                 BLUE/  
                 RED/ 
  
                 # The last one is where I will put the actual test problems and solution data.  Will remain somewhat consistent with my existing code.
                 configs/ 
                      # Maybe I'll do it like this:
                      blue_random_red_random/
                      blue_random_red_opt/
                      etc...
  

[jpdening]

Hi Dowon, I will review this tonight. Going to my grandmother’s birthday dinner.

…

-Jeremy Get Outlook for iOS<https://aka.ms/o0ukef>

________________________________ From: Dowon Lee ***@***.***> Sent: Saturday, February 1, 2025 4:59:27 PM To: jpdening/Visibility-Project ***@***.***> Cc: Subscribed ***@***.***> Subject: [jpdening/Visibility-Project] File structure for test problems and data (Issue #1) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi Jeremy, To organize our file structure for the new test problems and analysis, here's what I am thinking: * 1. CLPSSitesRandomSats data (Visibility data for CLPS sites) * Add all orbits that you used for the genetic algorithm * Remove "Random" from CLPSSitesRandomSats folder name. (e.g. CLPSSitesVis) * 2. Add new folder named test_problems with the following structure test_problems/ T_fin_192.0_dt_30.0_site_locs_((1,30),(3,30))/ # Same naming pattern 3_3/ # <number blue>_<number red> # These csv files may or may not be necessary. If I am creating the random constellations, I will make these files for you. blue_random.csv # csv files of the random blue constellations, where each line is a constellation. red_random.csv # The following folders are the same as you did with the "BLUE" and "RED" folders in "AllConstellations". blue_random/ red_random/ blue_opt/ red_opt/ # The last one is where I will put the actual test problems and solution data. Will remain somewhat consistent with my existing code. configs/ # Maybe I'll do it like this: blue_random_red_random/ blue_random_red_opt/ etc... — Reply to this email directly, view it on GitHub<#1>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AY4SKNQTOECY7XXD3WMYIV32NU7T7AVCNFSM6AAAAABWJWCQXOVHI2DSMVQWIX3LMV43ASLTON2WKOZSHAZDKNBWGA4TANA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[dowonlee777]

Have a good time! Let me know if you want to meet this week to discuss it. (Btw it'll be easier to view the contents on github, sorry about the mess in the email)

…

-dowon From: jpdening ***@***.***> Sent: Saturday, February 1, 2025 5:03 PM To: jpdening/Visibility-Project ***@***.***> Cc: Dowon Lee ***@***.***>; Author ***@***.***> Subject: Re: [jpdening/Visibility-Project] File structure for test problems and data (Issue #1) You don't often get email from ***@***.******@***.***>. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi Dowon, I will review this tonight. Going to my grandmother's birthday dinner.

-Jeremy Get Outlook for iOS<https://aka.ms/o0ukef>

________________________________ From: Dowon Lee ***@***.***<mailto:***@***.***>> Sent: Saturday, February 1, 2025 4:59:27 PM To: jpdening/Visibility-Project ***@***.***<mailto:***@***.***>> Cc: Subscribed ***@***.***<mailto:***@***.***>> Subject: [jpdening/Visibility-Project] File structure for test problems and data (Issue #1) You don't often get email from ***@***.***<mailto:***@***.***> Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Hi Jeremy, To organize our file structure for the new test problems and analysis, here's what I am thinking: * 1. CLPSSitesRandomSats data (Visibility data for CLPS sites) * Add all orbits that you used for the genetic algorithm * Remove "Random" from CLPSSitesRandomSats folder name. (e.g. CLPSSitesVis) * 2. Add new folder named test_problems with the following structure test_problems/ T_fin_192.0_dt_30.0_site_locs_((1,30),(3,30))/ # Same naming pattern 3_3/ # <number blue>_<number red> # These csv files may or may not be necessary. If I am creating the random constellations, I will make these files for you. blue_random.csv # csv files of the random blue constellations, where each line is a constellation. red_random.csv # The following folders are the same as you did with the "BLUE" and "RED" folders in "AllConstellations". blue_random/ red_random/ blue_opt/ red_opt/ # The last one is where I will put the actual test problems and solution data. Will remain somewhat consistent with my existing code. configs/ # Maybe I'll do it like this: blue_random_red_random/ blue_random_red_opt/ etc... - Reply to this email directly, view it on GitHub<#1>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AY4SKNQTOECY7XXD3WMYIV32NU7T7AVCNFSM6AAAAABWJWCQXOVHI2DSMVQWIX3LMV43ASLTON2WKOZSHAZDKNBWGA4TANA>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***<mailto:***@***.***>> - Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHRUODWDXDSNWJXO73RURVT2NU773AVCNFSM6AAAAABWJWCQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMRZGEZTGNRXHE>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[jpdening]

Hi Dowon,

I used 2756 orbits for the genetic algorithm. While running the genetic algorithm, I did not pre-generate visibility information to save on memory; instead, I generated the data whenever a new satellite was inserted (through mutation) or when a new constellation was inserted (through population death). I don't have an exact measure, but it would probably be about 1-1.5 gigs to include all of them here. Do you think that is necessary? I can include them if you think it would be useful.

I would like to possibly meet this week or next week to discuss how to organize all of this, because I'm somewhat unclear on what all of these fields are for the test_problems folder. Is this folder how you want to arrange your results, or do you need me to generate/re-arrange data to fit it? It would probably be faster for me to ask questions in person or over Teams.

-Jeremy

[dowonlee777]

Are you available tomorrow or Wednesday 10 AM? I'll be in the lab.

[jpdening]

I’m available tomorrow. I’ll see you at 10 sir.

…

-Jeremy Get Outlook for iOS<https://aka.ms/o0ukef>

________________________________ From: Dowon Lee ***@***.***> Sent: Monday, February 3, 2025 9:57:31 PM To: jpdening/Visibility-Project ***@***.***> Cc: Jeremy Dening ***@***.***>; Comment ***@***.***> Subject: Re: [jpdening/Visibility-Project] File structure for test problems and data (Issue #1) You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Are you available tomorrow or Wednesday 10 AM? I'll be in the lab. — Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AY4SKNTNF77CIIR4SYPI5BL2OAUBXAVCNFSM6AAAAABWJWCQXOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMZSG4YDONJRHE>. You are receiving this because you commented.Message ID: ***@***.***>