What order should g_i.embeddedbeammat() for embedded beam row properties be?

Question

I have the following line 
 
 g_i .embeddedbeammat(( "MaterialName" , deadman_material_name ),( "E" , deadman_E ), ("Width", deadman_width),( "w" , deadman_unit_weight ),( "PredefinedBeamType" , 2 ),( "Lspacing" , deadman_spacing ),( "SkinResistance" , 2 ),( "Tmax" , 10000 ),( "Fmax" , 200 )) 
 
 I am not getting the Width to show in the embedded beam row material properties so to work around this I removed the ("Width", deadman_width) from the above line and wrote material_i .Width = deadman_width underneath. 
 
 However, had an issue with material being invalid and not allowing calculation to happen. It says you need to edit/delete the embedded beam row material and if you open and then close it (without editing anything), it works absolutely fine. Which is a little strange, think it might be due to the order of the material properties, hence asking this question.

Stefanos Papavasileiou · Answer

Dear Iman, 
 Indeed, you are close, but missing one parameter that is computed based on the width, which is the area. 
 When using Python scripting, we need to define all linked parameters so if you add ("A", deadman_area) the command should be successful. 
 The moment you open the GUI (graphic user interface) the command is fully executed which then correctly computes the area in the background, leading to a valid material.