Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Francesco Radica
    @Francyrad
    Obviously this number depends on the radius of your impactor and target. The mines are:

    R_target = 6.371e6 # m
    M_target = 5.972e24 # kg

    R_impactor = 3.389e6 # m
    M_impactor = 6.39e23 # kg

    done both with iron and basalt (tillotson)
    Francesco Radica
    @Francyrad
    Are there problems with ANEOS? Terminal said me that the line 7 was wrong and i had to change it manually to get the code start
    Like if the line 7 of all the ANEOS was shifted in some way. This is very strange
    For the rest the EOS moves as expected, the movement during the impact feels like exactly the science publication of 2012
    Jacob Kegerreis
    @jkeger
    It's actually correct that you don't get valid results there. The orbit you've asked for isn't valid: your speed at contact is only about half the escape speed, which means that the apoapsis (furthest distance) the impactor could reach on that orbit is ~1.16e7 m. So an initial separation of more than that is impossible.
    I've added checks to the code, so if you download the latest master you'll now get an error message telling you your separation is larger than the apoapsis
    I think I know what the ANEOS issue is, but what did the error message say?
    Francesco Radica
    @Francyrad

    Thank you to have worked on that, i'll do a pip upgrade later!
    Sorry i'm on windows now and i cannot go to ubuntu at the moment: Basically, if you donwload the standard eos and you set ANEOS, The terminal said to me (after ./run) something like:

    The id material of fosferite (or another material) at line 7 is not valid, it should be 200000001 (e.g.), not 20000002

    It's like that the material fosferite, at line 7 had the long id of the iron, the iron had the id of Fe85Si15 and the last one had the material of the fosferite, like if they are all shifted. Just try to re download EOS and use ANEOS, it will say that. To fix you have just to change this number with the one requested from the terminal

    Francesco Radica
    @Francyrad
    About the error you are right, making a collision at a speed that is lower than v esc of the target doesn't make sense. I remember however some old publication (canup??) that did some collisions at 5 km/s, so i naively replicated that. I checked in others publications and most are at 10-11 km/s as it should be with an earth or with a proto earth...., Thank you!
    Jacob Kegerreis
    @jkeger
    There's no fundamental reason you can't have a collision at under v_esc, it just requires some more complicated origin story for where the impactor came from
    Are you sure the EoS error didn't say something like "EoS file %s date %d does not match expected %d \nPlease download the file using examples/Planetary/EoSTables/get_eos_tables.sh"?
    If not, then please say what the error actually was
    And if so, then please read the message and do what it says :)
    Francesco Radica
    @Francyrad
    Nono, it didn't say that. I just finish a work and i'll go to ubuntu to reproduce the error
    Francesco Radica
    @Francyrad
    [00000.0] phys_const_print: H_0 / h = 100 km/s/Mpc = 3.240779e-18
    [00000.0] phys_const_print: T_CMB0 = 2.725500e+00
    [00000.0] ../src/./equation_of_state/planetary/sesame.h:load_table_SESAME():121: EoS file ./EoSTables/ANEOS_forsterite_S19.txt date 20201104 does not match expected 20201003
    Please download the file using examples/Planetary/EoSTables/get_eos_tables.sh
    To fix just correct 20201104 with 20201003 at line 7 of the aneos file
    The same thing must be done with the other 2. These ids are exchanged between the aneos eos
    Jacob Kegerreis
    @jkeger
    ...
    That's what I sent
    The error message tells you exactly what to do
    No?
    I don't really know what else to say
    Francesco Radica
    @Francyrad
    Yes at the end, i remembered only the part in the middle, sorry. I bealived that this was just a file error. So i reported it
    Francesco Radica
    @Francyrad

    Hello! I wanted to reproduce the Cuk and Stewart 2012 scenario to make a study. I've been able to reproduce the dynamics and EOS of both bodies, however it's been impossible to set an Earth with a spin of 2.3 hours, as the publication says. For an Earth of 1.05 Me and a Radius of 1.02 Re, I've been able to set a minimum of 2.7 hours. Not less. In case of a less value, it says:

    Iter 1(15),13(30): R0=0.548R_E R1=1.086R_E: tol=-1(0.01), -1(0.01)
    Iter 1(15),14(30): R0=0.5473R_E R1=1.091R_E: tol=-1(0.01), -1(0.01)
    Traceback (most recent call last):
    File "cs2012xy", line 32, in <module>
    spin_planet = woma.SpinPlanet(
    File "/home/francyrad/.local/lib/python3.8/site-packages/woma/main.py", line 2189, in init
    self.spin(
    File "/home/francyrad/.local/lib/python3.8/site-packages/woma/main.py", line 3477, in spin
    self._L2_spin_planet_fix_M_steps(
    File "/home/francyrad/.local/lib/python3.8/site-packages/woma/main.py", line 3275, in _L2_spin_planet_fix_M_steps
    self.planet.gen_prof_L2_find_M_given_R_R1(
    File "/home/francyrad/.local/lib/python3.8/site-packages/woma/main.py", line 1051, in gen_prof_L2_find_M_given_R_R1
    self.M = L2_spherical.L2_find_M_given_R_R1(
    File "/home/francyrad/.local/lib/python3.8/site-packages/woma/spherical_funcs/L2_spherical.py", line 320, in L2_find_M_given_R_R1
    raise ValueError("M tends to M_max. Please increase M_max")
    ValueError: M tends to M_max. Please increase M_max

    This may happens to a limit of the program? However it should not be to fission level. It would be interesting to study the rotational instability of planets with a SPH approach..

    And second: IN the post processing files there is not written the total mass, momentum and angular momentum of each planet, but only the total of them. Will it be possible to add more post processing in the future or there is a kind of a computability limitation?

    Let me know and thank you!

    Francesco Radica
    @Francyrad

    And the python script produce me a white cartesian. The script seems to do the work. It only says:

    Could not find gas gamma, assuming 5./3.
    Could not find gas gamma, assuming 5./3.

    <__array_function__ internals>:5: UserWarning: Warning: converting a masked element to nan.
    /home/francyrad/.local/lib/python3.8/site-packages/numpy/ma/core.py:711: UserWarning: Warning: converting a masked element to nan.
    data = np.array(a, copy=False, subok=subok)
    Saved earth_impact_000000.png
    Could not find gas gamma, assuming 5./3.
    Could not find gas gamma, assuming 5./3.
    Saved earth_impact_001000.png
    Could not find gas gamma, assuming 5./3.
    Could not find gas gamma, assuming 5./3.
    Saved earth_impact_002000.png

    And so on.

    earth_impact_005000.png

    I tried to change num_in_target and id_body. However in the tutorials is not clear what these values should rappresent.

    Still thank you for the patience

    Francesco Radica
    @Francyrad
    Problem solve, however every simulation that i do gives to me only 2 colors. It doesn't matter the EOS used. only the standard simulation is able to receive differents colors
    earth_impact_000000.png
    Francesco Radica
    @Francyrad
    problem solved editing "num_in_target = Number of target particle". I suggest to insert the phrase: "add there the number of the target particle", only to avoid confusion..
    Francesco Radica
    @Francyrad
    I wanted to use make movie logger to make a better movie, however i need to have the logger enabled. I tried to compile enabling it, but the compilation end in errors. Is there some other thing that i'm missing and that i need to activate to use the python script?
    Francesco Radica
    @Francyrad
    Schermata da 2021-03-17 03-33-34.png
    Matthieu Schaller
    @MatthieuSchaller
    The logger is likely not what you expect it to be and in any case it's not yet fully functional for production runs that involve more than gravity interactions. It is expected not to work in your case
    Francesco Radica
    @Francyrad

    Ok it's not a problem. I Just wanted produce a video like Kegerreis et al. did here:

    https://www.youtube.com/watch?v=WM-o0y_pfRw

    I mean, i can also add a black background with premiere pro, so there are no problems

    Matthieu Schaller
    @MatthieuSchaller
    If it's of any help, these were not done using the logger. Snapshot-based work only here
    Francesco Radica
    @Francyrad
    Ah perfect!
    Francesco Radica
    @Francyrad
    Another thing: it's also impossible to set a negative value for angles. For example i cannot set a -30° for a collision. To do so i must do all with arrays and it's less elegant. If i try to put a negative number, the program scripts all to do still a positive collision
    Francesco Radica
    @Francyrad
    -30.png
    For example this is what happens if i use -30°
    however i'd expect that the speed is directed downward, for example like cuk and Stewart Scenario
    Willem Elbers
    @wullm
    Is SWIFT guaranteed to always output non-Hubble units (Mpc instead of Mpc/h)? I know about "h-scale exponent" for data sets, but what about attributes like "Header/BoxSize"? It would be useful to have an attribute indicating this.
    Josh Borrow
    @JBorrow
    Yes
    There are no h factors in SWIFT
    Willem Elbers
    @wullm
    Thanks!
    JingyaoDOU
    @JingyaoDOU
    Hi, I am a new user of swift and I mainly use swift on planetary impact simulations. In terms of the initial planetesimals generated by WoMa or Seagen, is there any feature included in the swift that I could use to cool the planetesimals( velocity dumping and entropy forcing )? I found the '--enable-planetary-fixed-entropy' option which I assume is used for entropy forcing. What about the velocity dumping, do I need to alter the source code in order to do that?
    Matthieu Schaller
    @MatthieuSchaller
    @jkeger will be able to help here