painaz
Guest
warning: I'm not a ptc technician. before applying procedures do all backups of the case.
procedures tested on wildfire iv and
in the previous post I indicated a procedure to make modelcheck a task
specific using custom configuration files.
now we see how to automate procedures, for 100, 1000 files at a time
preliminary operations
I create a directory where modelcheck "down" files reports of what it does in batch mode
example:
x:\directory_departure\modelcheck
open the file
x:\dove_installed_proe\modchk\text\configconfig_init (first make a copy of it! ! ! ! )
I focus on voices:
# directory modelcheck will write reports on nt
#dir_report_nt $temp/mc_reports
# directory modelcheck will write reports on unix
dir_report_u /tmp/mc_reports
# directory modelcheck will write reports
#dir_report $temp/mc_reports
and I change that dir_report (check that there is no #, otherwise it is a comment)
dir_report x:\directory_di_partenza\modelcheck\mc_reports
for scruples I also put
# config select mode - automatic
or load config menu option 
# or ask user at start of pro/e session (a)
cnfg_select_auto yna y
(previous example on a, ask)
(if you have wildfire i, otherwise do before and mile on tools configure modelcheck)
I create a batch file that lists files to test.
the batch file to create the list will be:
echo
dir x:\dove_are_i_file\*.prt* x:\dove_are_i_file\*.asm.* /b /s > x:\directory_di_partenza\modelcheck\list.txt
in practice are listed only prts and asms of any numbering (that is why *.type.*) without additional information (option /b) of the indicated directory and subdirectory (option /s) and redirect list from the video to a list text file.txt (option > )
create a link (put it on x:\directory_di_partenza\modelcheck) that points to this file:
x:\dove_installed_proe\bin\modelcheck.bat
launch the command, appears:
selected batch modes, with "browse" pointed to list.txt created by list.bat
the proe/start command must simply point to x:\dove_installed_proe\bin\pre.exe
now modelcheck, grind, do what you have to do and create two reports, a text about
x:\directory_departure\modelcheck called list.txt.mc_tmp
an html "infognato" (I don't know if it is possible to indicate where to create it) on (in case you have xp)
x:\documents and settings\mio_username\dati application\ptc\proengineer\mdlchk
which is called: batch. list.t.summ.html
If you open it comes out like this:
[Bleep] [Bleep] [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep] [Bleep] [Bleep] [Bleep [Bleep] [Bleep] [Bleep] [Bleep [Bleep] [Bleep [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep [Bleep [Bleep] [Bleep] [Bleep] [Bleep [Bleep [Bleep] [Bleep] [Bleep [Bleep] [Bleep [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep] [Bleep [Bleep [Bleep] [Bleep] [Bleep [Bleep [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep [Bleep
wildfire the
the wildfire i does not have a "wizard", disogna fare tutto textuali
the command to launch has syntax:
modelcheck executable_proe -f file_list -c file_configuration_specifica
then you have to create a batch file of the type:
x:\dove_proe\bin\modelcheck.bat x:\dove_proe\bin\proe.exe -f x:\dove_list\ list.txt -c x:\dove_proe\modchk\text\config\config.gmc
if you have localized Italian, otherwise the configè on ....\usacii\config.gmc
Stop.
if you have suggestions or find errors the reports are well received.
procedures tested on wildfire iv and
in the previous post I indicated a procedure to make modelcheck a task
specific using custom configuration files.
now we see how to automate procedures, for 100, 1000 files at a time
preliminary operations
I create a directory where modelcheck "down" files reports of what it does in batch mode
example:
x:\directory_departure\modelcheck
open the file
x:\dove_installed_proe\modchk\text\configconfig_init (first make a copy of it! ! ! ! )
I focus on voices:
# directory modelcheck will write reports on nt
#dir_report_nt $temp/mc_reports
# directory modelcheck will write reports on unix
dir_report_u /tmp/mc_reports
# directory modelcheck will write reports
#dir_report $temp/mc_reports
and I change that dir_report (check that there is no #, otherwise it is a comment)
dir_report x:\directory_di_partenza\modelcheck\mc_reports
for scruples I also put
# config select mode - automatic
# or ask user at start of pro/e session (a)
cnfg_select_auto yna y
(previous example on a, ask)
(if you have wildfire i, otherwise do before and mile on tools configure modelcheck)
I create a batch file that lists files to test.
the batch file to create the list will be:
echo
dir x:\dove_are_i_file\*.prt* x:\dove_are_i_file\*.asm.* /b /s > x:\directory_di_partenza\modelcheck\list.txt
in practice are listed only prts and asms of any numbering (that is why *.type.*) without additional information (option /b) of the indicated directory and subdirectory (option /s) and redirect list from the video to a list text file.txt (option > )
create a link (put it on x:\directory_di_partenza\modelcheck) that points to this file:
x:\dove_installed_proe\bin\modelcheck.bat
launch the command, appears:
selected batch modes, with "browse" pointed to list.txt created by list.batthe proe/start command must simply point to x:\dove_installed_proe\bin\pre.exe
now modelcheck, grind, do what you have to do and create two reports, a text about
x:\directory_departure\modelcheck called list.txt.mc_tmp
an html "infognato" (I don't know if it is possible to indicate where to create it) on (in case you have xp)
x:\documents and settings\mio_username\dati application\ptc\proengineer\mdlchk
which is called: batch. list.t.summ.html
If you open it comes out like this:
[Bleep] [Bleep] [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep] [Bleep] [Bleep] [Bleep [Bleep] [Bleep] [Bleep] [Bleep [Bleep] [Bleep [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep [Bleep [Bleep] [Bleep] [Bleep] [Bleep [Bleep [Bleep] [Bleep] [Bleep [Bleep] [Bleep [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep] [Bleep [Bleep [Bleep] [Bleep] [Bleep [Bleep [Bleep] [Bleep [Bleep] [Bleep] [Bleep [Bleep [Bleepwildfire the
the wildfire i does not have a "wizard", disogna fare tutto textuali
the command to launch has syntax:
modelcheck executable_proe -f file_list -c file_configuration_specifica
then you have to create a batch file of the type:
x:\dove_proe\bin\modelcheck.bat x:\dove_proe\bin\proe.exe -f x:\dove_list\ list.txt -c x:\dove_proe\modchk\text\config\config.gmc
if you have localized Italian, otherwise the configè on ....\usacii\config.gmc
Stop.
if you have suggestions or find errors the reports are well received.